Our new app was loading nicely on the iPhone.. .we externalized a lot of code 
to scripts that are meant to be used in front, back and as behaviors… with the

go stack

cmd


logInfo "Loading frontscript" && tStackPath

go stack (getPathForSharedLibraries() & tStackPath)

insert the script of stack tStackName into front


and like this:


put getPathForSharedLibraries() & "mobilecontrols.livecodescript" into 
tBehaviorStackPath

logRaw "info",tBehaviorStackPath

go invisible stack tBehaviorStackPath

I have a gut feeling that this might not be happy on mobile.

Any insights? sometimes my "suspicions" are completely wrong.

But on the iPHone when it starts up we get a black screen… and a whole series 
of iPhone answer dialogs, one after another that are not in our code. all the 
groups on the home screen are being declared with an "OK" button.

homeHeaderNavBat
OK

portal_links  # a big group on card 1
OK

home_gems # a subgroup of the above on cd 1
OK…

ten of these, declaring every single group on the card of the stack that is 
trying to be loaded "home.livecode"  and if we click OK on each one. finally 
the finish and the loader stack is sitting there, but not the stack that is 
supposed to be the first one to appear.

Really weird.




_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to