On 09/12/04 14:47:14, Sven Neumann wrote:
Tor Lillqvist <tml@xxxxxx> writes:
> I guess there is a mismatch in the ways of thinking here: GIMP > thinks that writing to stdout means the output will mostly go > somewhere where the user doens't see it, unless he explicitly does > something unusual (starts GIMP from the command line). > > The Win32 code in GLib again thinks that g_print() etc messages are > *important*, and supposed to be shown to the user in some way, even > opening a new console window if there isn't one already. If the > user wants to redirect stdout and stderr (to NUL: or a file), he > can do it from the command line.
There got to be a way to change this behaviour of g_print(), no?
Regardless on what's done in the glib side, why not using g_set_print_handler and g_log_set_handler, as Alif Wahid suggests, to redirect the messages to the Error Console? I, for one, as a user of the Win32 version expected to find the messages there and when they were shown in a different window I wondered why. Perhaps it's also better under Linux so that the messages aren't lost if the user doesn't open gimp from a console.
-- Pedro Gimeno
