Design Patterns: MenuBar, StatusBar, etc.

Oliver Schoenborn wrote:
>> -----Original Message-----
>> From: Michael Hipp [mailto:MichaelHipp.com]

>>
>> Thanks. That's a good thought and I use it other
places. Just 
>> not sure how to make it work in this case where
I'm using the 
>> status bar to display error and informational
messages that 
>> might be generated in a myriad of places -
sometimes down in 
>> the data-related (model) code and sometimes high up
in the 
>> GUI. The status bar would have to know about a long
and 
>> ever-changing list of things to subscribe to.
> 
> Personally I find status bars useful only for a certain
class of information
> that does not include what you are describing. I find
users often forget to
> look at the status bar. Even stuff as simple as the
"security state" (eg in
> FireFox) is easy to forget to look at. For what you
describe I would use a
> logging mechanism with a log window that can be
shown/hidden if the user
> wants. If the message is really important, show it in a
message box. It also
> becomes difficult to control that only one message goes
to the status bar
> for any given "user event".  

Yes. Food for thought.

Thanks,
Michael


------------------------------------------------------------
---------
To unsubscribe, e-mail: wxPython-users-unsubscribelists.wxwidgets.org
For additional commands, e-mail: wxPython-users-helplists.wxwidgets.org