System: Debian, Sarge
It seems the different demo's don't give feedback
in a consistent way. Some of them give their feedback
in the lower subwindow of the demo others simply
put it in the console from which I started the demo.
--
Antoon Pardon
Antoon Pardon wrote:
System: Debian, Sarge
It seems the different demo's don't give feedback
in a consistent way. Some of them give their feedback
in the lower subwindow of the demo others simply
put it in the console from which I started the demo.
The demo is also my main test suite, and I often put debugging messages in as print statements. They will go to the console. Messages written to the log object passed to each sample go to the window.
If this is too annoying for you I accept patches. 
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
I don't mind that messages can go to either the console or
the message, but my impression is, that it is not done
consistently. I've seen debug messages in the window and
I have seen things that look like a feedback to what I
did, on the console.
I'm willing to submit patches, but that seems futile
if there is no guiding line for the future on what
should be sent where. Feedback to show the program
is respondig to user actions to the window,
debugging information to the console, seems the
most appropiate.
On Wed, Mar 26, 2003 at 11:05:35AM -0800, Robin Dunn wrote:
Antoon Pardon wrote:
>System: Debian, Sarge
>
>It seems the different demo's don't give feedback
>in a consistent way. Some of them give their feedback
>in the lower subwindow of the demo others simply
>put it in the console from which I started the demo.
>The demo is also my main test suite, and I often put debugging messages
in as print statements. They will go to the console. Messages written
to the log object passed to each sample go to the window.If this is too annoying for you I accept patches.
--
Antoon Pardon