Re: [Gimp-developer] Console window on Win32
gtk-app-devel-list people, check the start of this thread from the gimp-developer archives at http://www.mail-archive.com/gimp-developer%40lists.xcf.berkeley.edu/msg07988.html Sven Neumann writes: There got to be a way to change this behaviour of g_print(), no? Well, one could redirect stdout and stderr to /dev/null (i.e. NUL: on Windows), either in the command line that starts GIMP, or even in GIMP itself with freopen(). If stdout or stderr are connected to NUL:, they aren't invalid, and g_log() won't open any console window. One could even go so far that if there is a consensus among GTK+ app developers (whose apps run on Win32) that the opening of console windows in GLib was a silly idea and has been of little use, that code could just be removed. g_print() etc would then write to stdout or stderr, like on Unix, regardless of whether they are connected to anything or not. It would then be the end user's responsibility to redirect stdout/stderr of a GUI application to a file if they want to see whatever might be written to stdout/stderr. Could we have a raise-of-hands here? Who thinks GLib shouldn't bother doing that console window allocation stuff at all? Personally I don't have any preference. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Console window on Win32
Hi, Tor Lillqvist [EMAIL PROTECTED] writes: Could we have a raise-of-hands here? Who thinks GLib shouldn't bother doing that console window allocation stuff at all? +1 Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Console window on Win32
On Sunday, September 12, 2004, 15:15:37, Tor Lillqvist wrote: Could we have a raise-of-hands here? Who thinks GLib shouldn't bother doing that console window allocation stuff at all? How about setting an environment variable? If something like OPEN_CONSOLE is set, open the console window when needed, otherwise not? Anyway, I'm in favour of not opening the console by default. It's easy enough to change a GUI program to open console on startup, if that's needed. -- Jernej Simoncic http://deepthought.ena.si/ for personal mail, replace guest.arnes.si with isg.si Formation of a party signals the dissolution of the movement. -- Political Postulate ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Console window on Win32
Hi, Tor Lillqvist wrote: Could we have a raise-of-hands here? Who thinks GLib shouldn't bother doing that console window allocation stuff at all? Me too. I hate threads that degenerate into this, but it's the most annoying thing possible in a GUI app :) Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Console window on Win32
On 09/12/04 14:47:14, Sven Neumann wrote: Tor Lillqvist [EMAIL PROTECTED] 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 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Two questions
Hi, I have 2 questions, 1. When will the 2.2 be released? I hope to complete translation when 2.2 be available. 2. In 2.2, I also hope when press F1 in Gimp (LANGUAGE=zh_CN or LC_ALL=zh_CN.GB2312, zh_CN.UTF-8...) , it will open the right chinese docs. Regards, Cai Qian ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
