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.
On 7/10/2017 10:44 AM, Bob Sneidar via use-livecode wrote: > I'm going to have to disagree here. I open windows modally for the specific > purpose of halting code in the calling stack until the modal window is > dismissed so that I can proceed with input from the user. An Answer dialog is > simply a modal stack if I am not mistaken. It's interesting though that a > hidden window is not modal. I will have to experiment with that. > > Bob S > > >> On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> (modal blocks underlying windows, not necessarily code) > > _______________________________________________ > 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
