Hi,
whenever one reads some of the public forums about GIMP there's one
problem on the Win32 platform that shows up over and over again:
Whenever GIMP or any library that GIMP is using writes something to
stdout/stderr, on Win32 a console window is opened. There is really no
reason a user should
Hi,
Alif Wahid <[EMAIL PROTECTED]> writes:
> > > I noticed that GIMP uses message output and debugging functions
> > > provided by GLIB. So isn't it possible to fix this by just setting a
> > > custom print handler using g_set_print_handler and so on? That would
> > > make it portable as well. Ju
Sven Neumann writes:
> Almost all of the messages that cause this problem don't come from the
> GIMP application. They are created by libraries that we are using and
> these libaries aren't necessarily using g_print() and g_printerr().
Nope, you have it backwards. 3rd-party libraries who write
Hi,
> It would be possible to make it impossible to close the console window
> that GLib opens, by removing the close button from it. Then users
> would know just to minimize it if they aren't interested in the
> messages. See my last comment in bug #141102.
It's often a habitual thing for window
Hi Tor,
I've played around with the g_set_print_handler and the
g_log_set_handler functions and they certainly stop the console window
from coming up when I use my custom handler to redirect the message to
somewhere else. So it may well be a good way to give the user an
option of redirecting these
Hi,
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 lin
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
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.berk
On Sun, 12 Sep 2004 13:15:37 +, Tor Lillqvist <[EMAIL PROTECTED]> wrote:
> 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
On 12 Sep 2004 15:16:21 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:
> 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
>
>
> __
Replying to your own message is a sign of insanity. Guilty as charged. :)
On Sun, 12 Sep 2004 12:47:44 -0400, Nathan Summers <[EMAIL PROTECTED]> wrote:
> On Sun, 12 Sep 2004 13:15:37 +, Tor Lillqvist <[EMAIL PROTECTED]> wrote:
> > Sven Neumann writes:
> >
> > One could even go so far that
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
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 Near
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 unusu
Hi,
Pedro Gimeno Fortea <[EMAIL PROTECTED]> writes:
> 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
Hi Tor,
> Could we have a raise-of-hands here? Who thinks GLib shouldn't bother
> doing that console window allocation stuff at all?
I support this idea, that GLIB shouldn't bother opening a console
window at all. Cheers.
Alif.
--
"Heaven is the peaceful place on earth...New Zealand."
--
On 09/13/04 11:04:06, Sven Neumann wrote:
The messages aren't meant for user's eyes, I think I mentioned
that. The messages don't make any sense for the user and should only
ever seen by developers or when we ask users to start gimp from a
console window and to tell us if there are messages to be s
Hi,
Pedro Gimeno Fortea <[EMAIL PROTECTED]> writes:
> On 09/13/04 11:04:06, Sven Neumann wrote:
>
> > The messages aren't meant for user's eyes, I think I mentioned
> > that. The messages don't make any sense for the user and should only
> > ever seen by developers or when we ask users to start
> No. The user is not supposed to see them, never. Actually no such
> messages should ever be emitted. If it does, there's a programming
> error. It would not help to show these messages to the user.
What about a user who wants to file a bug report? Surely
they are relevant in that case?
Best,
William Skaggs writes:
> What about a user who wants to file a bug report? Surely
> they are relevant in that case?
They can then start the GUI app with explicit redirection of stdout
and stderr to a file.
--tml
___
Gimp-developer mailing list
[EMA
]
]> Doesn't it make sense to prefix Glib errors
]with something like: "Glib
]
]> Error:" or "System Error:" or "Gimp Error:"
](localizing just that
]> string) and let the rest appear as-is within
] the error console?
]
]No. The user is not supposed to see them, never. Actually no such
]mess
On Mon, Sep 13, 2004 at 05:39:00PM +0200, Sven Neumann wrote:
> Hi,
>
> Pedro Gimeno Fortea <[EMAIL PROTECTED]> writes:
>
> > On 09/13/04 11:04:06, Sven Neumann wrote:
> >
> > > The messages aren't meant for user's eyes, I think I mentioned
> > > that. The messages don't make any sense for the u
[EMAIL PROTECTED] writes:
> The messages would ideally be able to be shown in a real window
> (not the console)
And what's so unreal about a console window? Is is just that they
are black and white and make (some) people think of MS-DOS?
(Some call console windows "DOS boxes" and seem to think "
On Monday, September 13, 2004, 23:26:52, Tor Lillqvist wrote:
> The consensus so far seem to be that GLib should not open any
> console windows by itself. OK, fine with me, such a change could
> be done even in the stable branch (2.4.x) IMHO. But I certainly
> hope that it doesn't mean that people
Hi Tor,
> The consensus so far seem to be that GLib should not open any
> console windows by itself. OK, fine with me, such a change could
> be done even in the stable branch (2.4.x) IMHO. But I certainly
> hope that it doesn't mean that people then will start whining
> that they want "log windows
Here's what a log window would look like:
A log window would have a button that says
"Clear" to clear the log and one that says
"Close" to close the window, and maybe something
that says what file to tee. Nothing should
shutdown the GUI unless clearly marked and
accompanied by a clear confirma
Hi,
It doesn't make sense to have such log windows as a part of GLIB.
Sounds like this sort of log window could really come in handy as part
of GTK perhaps?
I think somehow the console window can be made closeable but when
closed, doesn't shut down the whole app, then that would be ideal
solution
See KB article 818361 concerning
disabling the close button on the title bar.
This seems to be the important part:
hWnd = ObtainWindowHandle(name);
hMenu = GetSystemMenu(hWnd, false);
DeleteMenu(hMenu, 6, 1024);
I haven't tried it. You probably have the
window handle and don't need the first l
Harring,
The serious problem is not that the dos console looks scary,
although it is ugly, that would be ok for ms windows.
The problem is that windows hangs any application with
a console window if someone happens to click on the text
in the box, for example, to copy it, or by accidentally
touc
On Fri, 17 Sep 2004 18:59:38 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> However, it is in our power
> to work around the problem. One such workaround is to only
> use a console if a command line option (like --console)
> or an environment variable is set.
Since gtk already meddles wit
I wrote:
> > Except that on Windows it's not "or", but "and". Just starting a GUI
> > application from a command shell in a console window doesn't make its
> > stderr and stdout connected.
Iago Rubio writes:
> True, but I think my point of view is still valid. No Windoze app opens
> a console
Tor Lillqvist wrote:
I wrote:
> > Except that on Windows it's not "or", but "and". Just starting a GUI
> > application from a command shell in a console window doesn't make its
> > stderr and stdout connected.
Iago Rubio writes:
> True, but I think my point of view is still valid. No Windoze ap
Michael Schumacher writes:
> When started from the MinGW (and probably Cygwin) bash, this doesn't
> happen. The output appears in the same console (rxvt window).
Wow. Didn't know that. I seldom use MSYS and its rxvt. I assume rxvt's
window isn't a console window, it's a normal "graphics" window
> Few end-users have rxvt, though.
huh, that is wrong, many people in Asia really perfer it, coz its nice
wide-width characters handling.
Regards,
Cai Qian
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo
On Sunday, September 19, 2004, 15:13:31, Cai Qian wrote:
>> Few end-users have rxvt, though.
> huh, that is wrong, many people in Asia really perfer it, coz its nice
> wide-width characters handling.
Does that include Windows users?
--
< Jernej Simoncic ><><><><>< http://deepthought.ena.si/ >
<
> Does that include Windows users?
No, only those Cygwin people.
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
36 matches
Mail list logo
