Peter- Saturday, September 29, 2012, 11:36:34 AM, you wrote:
> However, I'm not sure I can use that solution. Won't lock messages apply to > the stack I'm opening as well as the stack which issues it? If so, that > could interfere with the opened stack's processing. Well, yes, that's the whole point. Are you trying to open a stack and simultaneously *not* open the stack? If you just want to load it into memory, the locking messages will do the trick. If you want to execute a different task, then you're at the mercy of whatever it does. -- -Mark Wieder mwie...@ahsoftware.net _______________________________________________ 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
