modal window = block handler? admin at
Mon Jul 10 22:51:28 CEST 2017

If “popup” is non-blocking then it’s a bug. However, I hope that the non-blocking behaviour of “open invis as modal” is retained, or there is no way to indicate progress in a modal.


Hugh Senior



From: Andre Garzia [mailto:andre at] 
Sent: 10 July 2017 19:15
To: How to use LiveCode <use-livecode at>
Cc: <admin at>
Subject: Re: modal window = block handler?




Just to add a related note here, at least on 9dp5 the "popup" command is also not pausing. It is supposed to pause the handler that calls it until menupick happens but in my experience here it simple keeps running even while the modal is open.


This might be related.


om om



On Mon, Jul 10, 2017 at 2:18 PM, via use-livecode <use-livecode at <mailto:use-livecode at> > wrote:

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

> I'm going to have to disagree here. I open windows modally for the
> 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
> 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 , via use-livecode <use-
> livecode at <mailto:livecode at> > wrote:
> >
> > (modal blocks underlying windows, not necessarily code)

use-livecode mailing list
use-livecode at <mailto:use-livecode at> 
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

-- -- All We Do Is Code. -- minimalist url shortening service.

More information about the use-livecode mailing list