On Sun, Nov 18, 2012 at 6:54 PM, Art Heimsoth <artst...@artheimsoth.com>wrote:
> In using the FIleNameDialog, when the dialog is being presented, if the
> underlying
> dialog is cancelled or another menu selected, it appears those options are
> active.
> If menu options are selected while the file dialog is displayed, they
> appear to be
> stacked and then executed after the file dialog returns - however, the
> cancel button
> does cancel the main dialog but not these "stacked" selections or the file
> dialog.
> Is this a case where the unguarded option should be used on these menu
> option
> methods?
>
>
You really should be passing in the window handle of the "underlying"
dialog as the second argument to the FileNameDialog() routine. This will
disable the underlying dialog until the file dialog returns.
Not doing that will give you unpredictable behavior similar to what you
describe. There is no good way to program for the unpredictable behavior,
the standard practice is to prevent it.
--
Mark Miesfeld
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
