[Kale]

@CelesteP wrote:

Hi:

So a link widget does not need to be “pressed”, it will just automatically go to the screen that I set it to?

A link widget works exactly as you would expect. It calls it´s target when it´s pressed. In this case it is a workaround, because the compiler seems to have a problem with screentransitions when there is no reference to the targetscreen. So the link widget is an invisible reference to the RESULTS screen in your case. It can not be seen by the user, but by the compiler 😉

Kale

[Celeste Patin]

Hi Kale, Octavio & Wayne:
I have included my file again below. I removed all of the pop-ups. I put a hidden link in the XWKLYScreen. When I run the XWKLYScreen through the emulator, it works. All the calculations work and it automatically links to the XRESULTS screen.

The problem is when I don’t run the XWKLY screen through the emulator first (i.e. I run the XCAS Screen first), the calculations do not work, the link does not automatically move to the XRESULTS screen and the XRESULTS screen is not updated.

I have not changed the XMTHLY or XANNUALLY screens yet since I would like to get the XWKLY working and find out what is wrong.

It seems like it is considering each screen separately instead of one application. What is causing this? Have you seen this before?

I added an X in front of the field name in the code for the WKLY screen so it would work with the X in the front.

Any ideas? Try running just the XWKLY–works, try running XCAS screen first and the XWKLY does not work. Help!

Thank you,

Celeste

Attachments:

You must be logged in to view attached files.

[Celeste Patin]

Kale, Octavio & Wayne:

I started from the beginning and began again to design the same app that is not working with the calculations and moving the result to another screen.

The new one is attached.

It is a simpler version. It has a HOME screen, INPUT, WEEKLY and RESULT screen. Again, when I generate the APP the calculations and moving the average to the other screen does not work. When I run the WEEKLY in the emulator by itself it works!

Please help!

Thanks,

Celeste

Attachments:

You must be logged in to view attached files.

[Kale]

@CelesteP wrote:

Hi Kale, Octavio & Wayne:
I have included my file again below. I removed all of the pop-ups. I put a hidden link in the XWKLYScreen. When I run the XWKLYScreen through the emulator, it works. All the calculations work and it automatically links to the XRESULTS screen.

The problem is when I don’t run the XWKLY screen through the emulator first (i.e. I run the XCAS Screen first), the calculations do not work, the link does not automatically move to the XRESULTS screen and the XRESULTS screen is not updated.

I have not changed the XMTHLY or XANNUALLY screens yet since I would like to get the XWKLY working and find out what is wrong.

It seems like it is considering each screen separately instead of one application. What is causing this? Have you seen this before?

I added an X in front of the field name in the code for the WKLY screen so it would work with the X in the front.

Any ideas? Try running just the XWKLY–works, try running XCAS screen first and the XWKLY does not work. Help!

Thank you,

Celeste

Hi,

make sure that when you generate the app, your XCAS Screen is seen. Then insert your .js code into the XCAS Screen_custom.js file.

It works perfectly on my side.

Kale

Attachments:

You must be logged in to view attached files.

[support-octavio]

Hi Celeste,

This is the problem, when you run your main design file, the customize code on your secondary screens are not copied automatically to the <main-file>_custom.js file. Please add all the customize code from your secondary screens to the <main-file>_custom.js file. This should works for you.

For more information, please see: http://www.genuitec.com/support-genuitec/viewtopic.php?p=6485#p6485

[Celeste Patin]

Hi Octavio:

Thank you very much. It does work putting all of my coding in the “home” screen. There will be coding for other screens so does it matter which coding comes first (i.e. should coding for screen weekly come before coding for screen monthly, etc…) in the “home” screen.

Thank you so much–you give me hope again that I can complete this project. It’s been a bit frustrating but I appreciate all of the help.

Celeste

[Kale]

Hi CelesteP,

it doesn´t matter where the code in your screenname_custom.js file is put in, as long you put it at the end of your .js file and not inside of predefined functions that will be called when a specific event triggers, such as page transitioning or when the document is ready (phoneui.documentReadyHandler = function() { } )

Also you don´t have to keep your code in a certain order.

Kale

[Author]

Posts