On 4/29/12 2:49 PM, Peter Haworth wrote:
Hi Alex, Thanks for the suggestion. That would work but I'm just not a big fan of the "splash stack" approach in general unless there's a genuine (at least in my opinion!) reason for having one, like an extended amount of time to initialise the program. In this case, I'd rather delay the user every time they run the program with a splash stack if the only reason for it is to deal with a situation that happens infrequently.
It doesn't have to actually display or wait. It can be set invisible on preopenstack and go immediately to the main stack. Then when you do an update, you could show it so the user has something to look at, and add a progress bar too if you want.
-- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ 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
