OIC! So it would be possible to set a global before the calling stack launches the "dialog", and have the dialog stack when it is returning control to the calling stack, lock messages, close itself, then open the stack stored in the global when it's finished and has saved all the user interaction in the dialogData. This would effectively prevent any initialization scripts or opencard/stack handlers from triggering when returning from the dialog stack. Would that do?
Bob On Jan 3, 2012, at 1:44 PM, J. Landman Gay wrote: > On 1/3/12 3:00 PM, Bob Sneidar wrote: >> Because rolling your own answer dialog is pretty easy, the typical >> answer to this question is roll your own. > > The problem with mobile apps is that only one stack can be open at a time, so > when the dialog opens, it closes the main stack and takes up the whole > screen. I don't think there's a way around that. Mobile apps are limited to > one card at a time. > > That said, it could possibly be faked by showing a group over the current > card, but everything else on the card would have to be disabled. Or maybe the > group could have a card-sized button at the back that just blocks mouse > actions, leaving only the "dialog" group active. > > -- > Jacqueline Landman Gay | [email protected] > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
