Hi Björnke, Am 20.03.2013 um 17:59 schrieb Björnke von Gierke <b...@mac.com>:
> There's a lot of stuff that doesn't work on preopenstack if your stack is the > premier mainstack of a standalone. This includes liburl, all externals, url > (files too), and some other things. but this is caused by the way Livecode loads all of these libs and externals! So I don't think you can compare this with the below mentioned problem. OK, the result is the same in the end :-D > Just now someone couldn't speed up a complex object creation with "lock > screen", so it seems that doesn't work either. > > On 20.03.2013, at 17:20, Peter Haworth wrote: > >> Thanks for the suggestions everyone. Here's where I'm at. >> >> Craig: >> I moved the code to openCard, still the same problem. >> >> Mike: >> wait zero didn't fix it, nor did send in time with full path. >> >> Mark: >> Restructuring the code does, of course, work and is probably going to have >> to be my workaround. The reason I didn't really want to do that is that the >> mouseUp event can be sent to one of 7 buttons (it's all to do with the >> user's startup preference settings) so there's a significant amount of code >> to be moved around but it's looking like I may have to. >> >> In general, it seems that using preOpenCard on the main stack just isn't >> reliable. I remember in another project I had to move ALL of my >> preOpenCard processing into a separate handler and call it from preOpenCard >> with a wait zero before it. Without that structure, the code would just >> stop executing at what looked like a pretty harmless statement >> without throwing any type of runtime error. >> >> Pete Best Klaus -- Klaus Major http://www.major-k.de kl...@major.on-rev.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