On Wed, Jul 26, 2000 at 11:35:30AM -0600, Mitch Chapman wrote:
> It may be that I'm solving the wrong problem. In other words,
> there may be a better way to present the information that's
> currently being displayed in these modeless dialogs. But if
> y'all have any suggestions for how to solve this specific
> problem, I'd be grateful.
The correct solution would be to fix the customer :-)
The reason why you cannot iconify modal dialogs independently
of your application is the human brain: Just imagine, your
working with your app and then suddenly, one of the modal
dialogs is in your way and you iconify it. Now you do
what you wanted when the dialog got in your way. After
some time, you go back to your app and try to continue
to work with it. But now it "hangs". You try everything
and after some time kill the app and start it again because
you didn't remember that there was an iconified modal dialog
which blocked the "hanging" application.
Conclusion:
- Don't use modal dialogs. Disable gadgets instead. This
gives the user a visual feedback of what is going on
unlike the modal dialogs. What you can do is you can
disable the main window of the application. This will
make the (non-modal) dialogs independent of it and you
can iconify every window indepently. Also, a user
will now see right away why he cannot work with the
application.
--
==============================================
Sowatec AG, CH-8330 Pfäffikon (ZH)
Witzbergstr. 7, http://www.sowatec.com
Tel: +41-(0)1-952 55 55
Fax: +41-(0)1-952 55 66
----------------------------------------------
Aaron "Optimizer" Digulla, [EMAIL PROTECTED]
==============================================
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
