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
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
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
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
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
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
snip...
Ill try to do something on the tool in the next time, but as always I
cannot
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.
On Mon, Jan 10, 2000 at 10:29:29AM +0100, Sven Neumann wrote:
Oops, I thought (but should have checked) that image_set_resolution_invoker
was calling the gimp_image_set_resolution() in app/gimpimage.c. And probably
it should since the core function keeps the undo_stack in sync by calling
Hi,
I have changed the core so that it does not accept zero resolutions.
Additionally I have changed all plug-ins that try to set the resolution
to check the value and simply don't set it at all if it is invalid. Gimp
will then use the default set up by the user.
Perl, IIRC
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
Matt.Wilkie writes:
I'm getting this weird display problem with some PNG
images, a sample is attached. Please let me know if
you do/don't have similar problems.
The PNG apparently claims to have the display (and print) resolution
of 0 pixels/inch... Set it with ImageScale
I have changed the core so that it does not accept zero resolutions.
Additionally I have changed all plug-ins that try to set the resolution
to check the value and simply don't set it at all if it is invalid. Gimp
will then use the default set up by the user.
Please make sure that XCF
On Sat, Jan 08, 2000 at 11:16:45AM +0200, Tor Lillqvist wrote:
The PNG apparently claims to have the display (and print) resolution
of 0 pixels/inch... Set it with ImageScale ImagePrint Size Display
UnitResolution X and Y and the image appears. The PNG plug-in
probably should check for this
13 matches
Mail list logo
