- This topic has 3 replies, 2 voices, and was last updated 11 years, 8 months ago by
.
-
Posts
-
Hi….If anyone would help it would be great…
The problem is that when I use a form twice in one of builds, I get some sort of duplication error:
Let me explain……
I have an app that has two menu buttons pointing towards to separately named screens
Example….The first menu button points towards “Survey Sreen 1” that has multiple Q/A inbuilt into it. The second menu button points towards “Survey screen 2” which has the same scenario.
Why does only one screen work in “Live Mode”, and not the other. (Usually the one that is built last)
Would there be some elements that are repeated in both screens conflicting? not sure…..
Hope you can understand the question?
Cheers
Col
>Why does only one screen work in “Live Mode”, and not the other. (Usually the one that is built last)
From your problem description some things are unclear to me.
>Why does only one screen work in “Live Mode”, and not the other. (Usually the one that is built last)
This statement leads me to guess that you may be using the designer incorrectly to build your app.
Your app has 1 file that is the 1st screen the app loads. This is the startup file and you should set the startup file property on this screen ONLY. Do not enable the startup screen property on any of your other screens.
When you want to preview your app in the Test Center, load the startup screen in the Designer and click the Run in Test Center button or menu action. This action will generate the code for the startup screen and any screen it is connected to via a GotoScreen action or a .mobi file included as in the startup screen’s Additional Files property. Do not include .mobi files that naturally reference each other in a screen flow connected by GotoScreen actions (that is redundant). All of the code for your app will be generated in a subdirectory with this naming pattern: <startupfilename>-www/
Lastly if you preview any non-startup screen in the Test Center, the designer unfortunately will generate code for it in a subdirectory similar to that of the startup screen. Many users incorrectly infer that these non-startup www foldrers of code are useful. Actually they are not and you should delete them asap since they are transient working files needed the Test Center for preview-only support.
Let us know if any of this is helpful. If you need to follow up you will need to provide more specific details and since this is development posting a small example goes a long way to helping everyone understand the problem in a common way.
The screens are “referenced” only to the start up screen via gotoscreen and back buttons…that is it. This logic should work.
There is only one start up screen:
Start up screen example:
Start up…goes to quiz 1 when you press quiz 1 link/button
Start up…goes to quiz 2 when you press quiz 2 link/button
which are both on the start up screen.
I also have issues with screens just stopping working out of the blue when you replace text in them and save…then re-build?
Thanks for any suggestions.
Col
Thanks for the follow up. Your app’s screen flow sounds very basic and typical for the designer to work with. It’s impossible to debug from a text description.
1) please share environment details on how you are testing your project, e.g., using Run in Test Center, native app testing on iphone5/iOS6, …
2) please share a small example project that replicates the problem. Once we can see what you are seeing then it is usually a quick fix.
