Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Tue, Jan 11, 2000 at 07:16:22PM +, Nick Lamb <[EMAIL PROTECTED]> wrote: > > Now if only all errors, debug messages and so on could use g_message() > > instead of printf() (in some plug-ins), then everything would be > > perfect... > > Mmmm, well that was part of my sort of half-thought-through expectations, All of these discrepancies become because you (as well as me btw), assumed that "error console" is some kind of "error log". Instead it seems to be something different. While I would prefer an error log window myself (since it is soo convinient for older messages), I think the "Error Console" is not that thing. Wether that could be changed (making it an error log) is another question, but if, then I'd prefer a way to log warnings (or debugging messages) using the PDB, so I do not have to hardwire my own solution in perl anymore. > As it is, some PNG errors are reported to stderr, which is probably > not useful to anyone The problem is that developers probably won't notice, because they start gimp from an xterm often. It's "only" the users who get hurt ;*> -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Tue, Jan 11, 2000 at 06:15:11PM +0100, Raphael Quinet wrote: > So maybe what we need is a new option in the gimprc, something like: > make-error-console-visible-on-first-g-message-and-leave-it-open > If you set that to true, then the error console would do what you were > expecting. Or did I misunderstand this discussion? > > Now if only all errors, debug messages and so on could use g_message() > instead of printf() (in some plug-ins), then everything would be > perfect... Mmmm, well that was part of my sort of half-thought-through expectations, we should see a lot MORE messages in a thing like the Error Console because we don't have to click "OK" for every single message... e.g. In the PNG plug-in, if I knew I was talking to the console, I would feel happy to report blow-by-blow CRC errors which may occur a few dozen times in a single (corrupted) file. However as a user I don't want twelve OK buttons to hit if I haven't got the console :) As it is, some PNG errors are reported to stderr, which is probably not useful to anyone (but it's default libpng behaviour so I have never gotten around to turning it off) and all fatal errors are reported via one or two general purpose g_message-type calls. Nick.
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Tue, 11 Jan 2000, Nick Lamb <[EMAIL PROTECTED]> wrote: > On Tue, Jan 11, 2000 at 11:50:28AM +0100, Sven Neumann wrote: > > As said, I can't reproduce your problem here. As soon as I open the > > error_console, all errors produced with g_message () appear in that > > dialog instead of popping up a message window. > > Oh, I see. Somehow I expected that all my errors would appear in that > box, regardless of whether they happened before it was visible. Having > played with that part I see what you mean... So maybe what we need is a new option in the gimprc, something like: make-error-console-visible-on-first-g-message-and-leave-it-open If you set that to true, then the error console would do what you were expecting. Or did I misunderstand this discussion? Now if only all errors, debug messages and so on could use g_message() instead of printf() (in some plug-ins), then everything would be perfect... -Raphael
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Sven Neumann wrote: > > > I don't see your problem. I do get my errors in the error-console. All > > > that's missing IMO is a way to set the error_console as the default > > > error_handler in the preferences. That should be easy and is definitely worth > > > the effort. > > Nick Lamb: > > Well, I think you hit the nail right on the head, I have seen this nice > > Error Console dialog, and never found out how to get my errors reported > > there. From your description it sounds like that's just some plumbing. > > > Sven: > As said, I can't reproduce your problem here. As soon as I open the > error_console, all errors produced with g_message () appear in that > dialog instead of popping up a message window. > I also see this error console, but never see anything *in* the error console. g_message() dribbles to dialog popups. Enlighten me: what sort of plumbing is involved? I've turned a couple of spigots, nothing comes out of pipes. Be good, be well. Garry Osgood
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Tue, Jan 11, 2000 at 11:50:28AM +0100, Sven Neumann wrote: > As said, I can't reproduce your problem here. As soon as I open the > error_console, all errors produced with g_message () appear in that > dialog instead of popping up a message window. Oh, I see. Somehow I expected that all my errors would appear in that box, regardless of whether they happened before it was visible. Having played with that part I see what you mean... I'm still not sure quite what I wanted this to do, but it does *do* something useful so strike that from the Triage list. Nick.
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
> > I don't see your problem. I do get my errors in the error-console. All > > that's missing IMO is a way to set the error_console as the default > > error_handler in the preferences. That should be easy and is definitely worth > > the effort. > > Well, I think you hit the nail right on the head, I have seen this nice > Error Console dialog, and never found out how to get my errors reported > there. From your description it sounds like that's just some plumbing. > As said, I can't reproduce your problem here. As soon as I open the error_console, all errors produced with g_message () appear in that dialog instead of popping up a message window. Salut, Sven
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
On Mon, Jan 10, 2000 at 01:56:01PM +0100, Sven Neumann wrote: > > * Error Console (well, here it is, but where are my errors?) > > I don't see your problem. I do get my errors in the error-console. All > that's missing IMO is a way to set the error_console as the default > error_handler in the preferences. That should be easy and is definitely worth > the effort. Well, I think you hit the nail right on the head, I have seen this nice Error Console dialog, and never found out how to get my errors reported there. From your description it sounds like that's just some plumbing. > > * Display Filters > > Are being worked on actively in the last time and the latest CVS version has > a working Gamma filter. Aha! Can someone talk about the intended use of the Gamma filter in Gimp? How does this interact with the (mostly unused) gamma-correction setting in the user's .gimp-1.1/gimprc file? I would like to be able (optionally) to reflect PNG image gAMA settings in the initial view of an image, and to save more accurate values for gAMA when images are entering/ leaving the digital domain. Right now, most users will just get 1 / 2.2 = 0.45 by default, but then almost all apps ignore/abuse the gAMA chunk anyway... Nick.
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Garry R. Osgood ([EMAIL PROTECTED]) wrote: > If there were one feature of Simon's path tool that I would like to have > automagically appear in the Integrated path selection tool, it is the ability > to manipulate the curve by "pulling" on it directly. it is a very pleasant > way to adjust curves. It's effect needs to be adjusted near control points; > bezier basis functions associated with the first and fourth control points > grow expotentially to unity, so manipulating Simon's path near control ^ infinity? > points can be a tad exasperating. Yeah. The basic idea is, that when you drag on the curve near an endpoint you dont want to change the curve at the other endpoint. So I have to move the handle from the near endpoint more drastically to achieve the "curve-dragging" effect. Maybe I should limit the ratio at some point... Anyway: It is not too hard to get the control-point back: Simply drag the curve near the anchor towards the anchor. The controlpoint will appear as quick as he went away earlier :-) Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Simon Budig wrote: > Sven Neumann ([EMAIL PROTECTED]) wrote: > > > How about some comments for feature triage? There are some features in > > > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > > Ill try to do something on the tool in the next time, but as always I > cannot promise anything. The first thing would be the API cleanup, the > second thing would be to prepare the conversion to a selection, but bound to > some strange events, since we need the Integration for the right way to > do it. If there were one feature of Simon's path tool that I would like to have automagically appear in the Integrated path selection tool, it is the ability to manipulate the curve by "pulling" on it directly. it is a very pleasant way to adjust curves. It's effect needs to be adjusted near control points; bezier basis functions associated with the first and fourth control points grow expotentially to unity, so manipulating Simon's path near control points can be a tad exasperating. Be good, be well Garry
Re: [gimp-devel] Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Sven Neumann ([EMAIL PROTECTED]) wrote: > > How about some comments for feature triage? There are some features in > > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > > at a time. Without paid staff to do this work, we must throw away [*] > > stuff that's not going to make it. On my short list... [...] > > * Paths > > Simon ? Umm - Yes. I´m terribly sorry, but at the moment my Dis-organizer works a little bit too well. A short summary of the state of the tool: Good News: * Manipulating the path works, maybe needs some minor cleanups. * Converting to a selection probably is easy, since there is code from Andy to convert an array of floats to an selection. * The code seems fairly stable - I dont get crashes at the moment. Bad News: * The API for new path types is not sane at the moment. At some points are Ints instead of floats, some functions do have too much parameters and so on. * The integration with the paths Tab in the L&C Dialog/the PDB Path API/ The XCF-Format is probably horrible - at least for me. Im not sure if this is on the TODO for 1.2, since there are lots of points, where we can break something. My point of view: If the Integration of the Paths tool could not be done before 1.2 we should not include the tool. Its use is too limited in the current state. It should be fairly easy to remove the files shortly before the 1.2 release if necessary. Ill try to do something on the tool in the next time, but as always I cannot promise anything. The first thing would be the API cleanup, the second thing would be to prepare the conversion to a selection, but bound to some strange events, since we need the Integration for the right way to do it. Hope this clears some things. Ill respond to questions... :-) Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/
Re: Triage! (was Re: [gimpwin-users] PNG blank display bug)
Hi, > It's the start of a new year, and my mind turns to Spring cleaning already > > How about some comments for feature triage? There are some features in > Gimp 1.1.x which are buggy or unusable, yet stay the same for weeks > at a time. Without paid staff to do this work, we must throw away [*] > stuff that's not going to make it. On my short list... > > * Resizable toolbar Yosh? I hope we can get the wrapboxes to work. They are considered to be part of GTK+-1.4, so it should be possible to fix this. As a workaround I'd suggest making the layout (horizontal, vertical) a preferences option and disable the interactive resizing. > * Natural airbrush Olof ? > * Error Console (well, here it is, but where are my errors?) I don't see your problem. I do get my errors in the error-console. All that's missing IMO is a way to set the error_console as the default error_handler in the preferences. That should be easy and is definitely worth the effort. > * Display Filters Are being worked on actively in the last time and the latest CVS version has a working Gamma filter. > * Paths Simon ? I think we can wait a little longer with the decision about the removal of the two new tools, Path and Xinput Airbrush, since they don't interact with any other part of the GIMP and can very easily be removed if necessary. Otherwise I'm all for pushing The GIMP into 1.2 as soon as possible. Salut, Sven
