Opening a modal as normal (i.e. visible) obviously still does what you specify. We simply have a 'hidden feature' that enables a non-blocking modal should it be required (e.g. a progress indicator that prevents user-clicks on other windows).
Hugh Senior FLCo > 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- > [email protected]> wrote: > > > > (modal blocks underlying windows, not necessarily code) _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
