lesson learned ...... happy i found out about this inconcistency now rather than later.
going forward I am using a "wait until mywindowopen = 0 with messages" to make sure i get the same identical behavior on every platform. thanks as always you guys On Mon, Jul 10, 2017 at 11:18 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Of course, modal windows do not "halt code execution" in that sense. They > could not because you would not be able to use any code in front or back > scripts. They prevent the calling handler from proceeding. It's like > inserting blocking code where the modal is called. > > Bob S > > > > On Jul 10, 2017, at 08:16 , Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > A related issue I ran into recently: > > > > I had a complex modal dialog. In my code for the dialog controls I was > > calling a routine that had a "wait 0 with messages" statement. I > > discovered that the wait ... with messages allows user events (for > > example commandKeyDown, etc.) to kick off other scripts while the modal > > dialog was still active under OSX. Windows still does a better job of > > modal actually being modal. This was an older stack under LC6.7.11, so I > > am not sure if the this is also applies to more recent versions. > > > _______________________________________________ > 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 > _______________________________________________ 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
