It looks like some strange things are happening in the Gimp (any
version since 1.1.x) if you create an image of size 1x63 or similar
sizes. Some of these effects (related to the tile management, IIRC)
had been discussed on this list in the past, but the strange thing is
that some people (Seth,
Since the GIMP/GNOME bug database has moved to bugzilla.gnome.org, the
administrative options have changed. On the old bugs.gnome.org, it
was possible for me to change the status of some bugs easily, but now
I cannot change the status, affected OS, priority and other features
of the bugs.
I
On Mon, 15 Jan 2001, Martin Weber [EMAIL PROTECTED] wrote:
I am no GPL expert, but I think it is compatible to GPL, but it does not
have a plugin interface.
[Lourens Veen [EMAIL PROTECTED] wrote:]
But is the license GPL compatible? And is it as flexible as the current
plugin system?
On Wed, 10 Jan 2001, [EMAIL PROTECTED] wrote:
On 9 Jan, Christopher Curtis wrote:
They do; if we started now to switch over to deltas then quite a few
people would complain about that. I definitely see the point, I'm behind a
very narrow pipe as well so I prefer patches, too, but what is
On Thu, 14 Dec 2000, [EMAIL PROTECTED] wrote:
This one covers a lot of things I previous mentioned in a bit better tone.
Quoting comes from Raphael Quinet's post #12115.
Wow, finally a person who understands my concerns, and is actually an
active gimp developer, so that things could really
Small addition to my previous message:
Basically, what we need for distributing the source code of the
plug-ins is a mechanism similar to CPAN, except that it should rely on
a tool or plug-in distributed with the Gimp and not on Perl. It could
also be extended for fetching binaries, but this
On Tue, 12 Dec 2000, Simon Budig [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
On most software packages (not for Linux, though), the
"underline" action keys are generally organized well enough so that it's
quicker to push that key instead of moving the mouse. For
On Sun, 19 Nov 2000, "Garry R. Osgood" [EMAIL PROTECTED] wrote:
I have attached a patch to gtk+-1.2.8/gdk/gdkinputcommon.h
that modifies gdk_input_common_find_events() so that it
will simply select device-specific event classes, given
an event_mask of GDK__MASK values, without imposing
On Tue, 14 Nov 2000, Simon Budig [EMAIL PROTECTED] wrote:
Garry R. Osgood ([EMAIL PROTECTED]) wrote:
[does GTK handle the XInput-devices and the "normal mouse" in the same way?]
At present, we know that is not entirely true in two mixes of hardware.
However, the manner in which they are
On Fri, 10 Nov 2000, David Monniaux [EMAIL PROTECTED] wrote:
I compiled Gimp under Solaris with --with-included-gettext. Trying to run
it with LANG=fr... does not yield anything translated. Nevertheless, Gimp
seems to load the translation file (seen in strace).
Has anyone else noticed this
On Fri, 10 Nov 2000, "wolfgang hofer" [EMAIL PROTECTED] wrote:
For painting Animations it can be useful
to see the previous or next frame(s)
more or less transparent.
Here are 2 Variants A) and B) how to implement such features in GIMP.
[...]
B) OnionLayer is a new 'special' layertype,
On Wed, 08 Nov 2000, Michael Natterer [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Raphael Quinet) writes:
Maybe we should all do our "mea culpa" and test a bit more seriously
especially on non-Linux platforms, now that 1.2 is just around the
corner.
Nope, it's just me wit
On Tue, 07 Nov 2000, Sven Neumann [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Raphael Quinet) writes:
I think that the best way to fix the screenshot plug-in is to add this
before the call to fork():
gimp_signal_private (SIGCHLD, SIG_DFL, SA_RESTART);
(don't forget to #include libgimp
Included below is a small test program that checks how the OS behaves
when a child process exits while the parent is blocking on waitpid()
and has a SIGCHLD handler installed (which also calls waitpid, and
thus could steal the status if the signal handler is called before
the first waitpid
On Wed, 08 Nov 2000, Ludovic Poitou [EMAIL PROTECTED] wrote:
Here's the results I got with your test program on Solaris 8, OSF1,
HP-UX, AIX.
[...]
Results on Solaris 8:
sigchld handler was called before waitpid (no status)
[...]
Results on OSF1- V4.0 True64 - alpha
sigchld handler was
On Mon, 6 Nov 2000, [EMAIL PROTECTED] wrote:
On 6 Nov, Sven Neumann wrote:
If you want me to change the helpbrowser, I need a detailed list of
the changes that are necessary.
just the changes we talked about: Removal of the HTML navigation bar
and using the supplied links in this bars
On Thu, 19 Oct 2000, "Uwe Koloska" [EMAIL PROTECTED] wrote:
to save some download time ;-) I tried to upgrade from 1.1.27 to 1.1.28
with the patch file. I found some minor problems; some files are
incorporated in their final form and not in the ini-form:
[...]
Another minor thing: the new
On Fri, 20 Oct 2000, Tuomas Kuosmanen [EMAIL PROTECTED] wrote:
On Fri, Oct 20, 2000 at 09:28:52AM +0200, thus said Raphael Quinet:
Another minor thing: the new splash screen is not included in the
patch. Maybe it is better to leave it out of the patch anyway,
because the splash screens
OK... Since the bug tracker seems to have lost the bug report that I
wrote last week and I don't want to re-type it until I am sure that it
will not be lost again, I will post a description of the problem
here...
Almost all File-Save plug-ins that are designed for single-layer file
formats
On Sun, 24 Sep 2000, "Dr. David Kirkby" [EMAIL PROTECTED] wrote:
I've built, gimp-1.1.25 on my Sun SPARCstation 20, using the following
pieces of software and hardware.
[...]
Gimp then builds okay, but crashes on startup. Debugging under gdb-4.18,
shows it seems to be looking for a source
On Sat, 9 Sep 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Thu, Sep 07, 2000 at 06:13:07PM +0200, Raphael Quinet [EMAIL PROTECTED] wrote:
the user installing the package is not the same as the one building
it. Some of these problems have been mentioned by Michael J. Hammel
two weeks ago
We all know that the usual "configure; make; make install" procedure
does not work exactly as advertised for versions 1.1.x, especially if
the user installing the package is not the same as the one building
it. Some of these problems have been mentioned by Michael J. Hammel
two weeks ago
Minor correction to my previous post: the library that is recompiled
twice is libgimpi.a (note the "i"), not libgimp.a.
The file libgimpi.a is created in the directory (top)/libgimp/, not in
(top)/libgimp/.libs/ as the other libraries under libtool's control.
-Raphael
On Wed, 07 Jun 2000, Sven Neumann [EMAIL PROTECTED] wrote:
[quoting Austin Donnelly [EMAIL PROTECTED]]
I would be very unhappy if changing the layer opacity from 100% to 50%
would eat up a dozen or more undo-steps since each value_changed signal
from the slider triggers an undo which
On Mon, 29 May 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Sun, May 28, 2000 at 06:46:43PM -0400, Warren Hedley [EMAIL PROTECTED]
wrote:
Also, configure ignores the perl executable argument specified
in the --enable-perl option (see configure line above, for example),
The
Well, it looks like I will not be able to attend the GIMP Developers
Conference at the end of this week (too bad - I really wanted to be
there), so here is an idea that could be discussed: there could be an
option to rotate a brush automatically according to the local tangent
of the path that the
While following Adrian's nice tutorial on Gimp Image Pipes, I tried
to load some PSP Tubes and see if I could convert them to Gimp's GIH
format, using gimp-1.1.21 under Solaris (sparc).
All of them failed with the error "PSP: Unrecognized block id ...".
This comes from a missing conversion from
Except for the vines and green pepper, the latest version of the Gimp
ships with basically the same set of brushes as version 1.0. Even the
gimp-data-extra package does not contain anything that demonstrates
the power of the pixmap brushes or pipes.
It would be good to add two or three
I just saw an article in comp.graphics.apps.gimp (in the thread with
the subject "White balance tool?") that starts describing a method
with these words: "use the color picker on the 'white' color,
duplicate the background layer, delete the original, add a layer..."
I had to read that twice to
On Tue, 16 May 2000, Jens Lautenbacher [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Raphael Quinet) writes:
I would even go as far as removing the "Add Alpha Channel" option from
the menus, and suggest that the prefered method to add transparency to
an image that has only
On Tue, 16 May 2000, Jens Lautenbacher [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Raphael Quinet) writes:
I still haven't found a good reason to keep the background layer
"special" when the image contains multiple layers. If the only
reasons are historical or to copy the featur
On Thu, 11 May 2000, Michael Natterer [EMAIL PROTECTED] wrote:
Raphael Quinet wrote:
No, actually it is not safe on all operating systems: as I wrote
elsewhere, you cannot always rely on SA_NODEFER. This means that in
some cases, you could miss a SIGCHLD signal that occurs while you
I uploaded the gimp_tips patch to ftp.gimp.org a few days ago, but
apparently it has not been moved out of the incoming directory yet,
and not comitted to CVS. Maybe some of you would like to have a
look at the updated file, so I have put it temporarily on this page:
On Thu, 11 May 2000, Michael Natterer [EMAIL PROTECTED] wrote:
Raphael Quinet wrote:
[...]
- SIGCHLD or SIGCLD: a child process died. This signal can be
delivered at any time. Some systems do not provide a reliable way
to know how many processes exited (if they do not support
On Thu, 11 May 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
[...]
What could be the case, however, is, that gimp itself does not reset it's
signal handlers when it execs the plug-ins. If this is the case, then this
bug (not restoring signal handlers to their default) might cause many other
On Wed, 10 May 2000, Michael Natterer [EMAIL PROTECTED] wrote:
Michael Natterer wrote:
Austin Donnelly wrote:
[ two mails i totally agree with ]
I'm about to commit some code which should bring the signal
stuff into a sane state. The ChangeLog entry is quite verbose
and
On Wed, 10 May 2000, Anton Enright [EMAIL PROTECTED] wrote:
I'm trying to get Gimp 1.1.21 to work correctly on Solaris 7
I've compiled the code fine this morning, and apart from the Error below
it runs fine:
gimp: shmat failed...disabling shared memory tile transport
This is very common
Posting a new version of the gimp_tips file caused some quick replies
with new tips. Thanks to Austin Donnelly, Andy Thomas and Garry
Osgood who sent some proposals. Here is a short unidiff (diff -U 0)
of the file, compared to the version posted yesterday. If there are
no more comments on it
I should have waited a bit more before sending my previous mail,
because I did not see Sven's reply on time...
On Fri, 05 May 2000, Sven Neumann [EMAIL PROTECTED] wrote:
[...]
Well, dragging does work, but using the icons as buttons instead of
a drag target is much faster and easier. You'll
lated tips. It will be easier for
# other people to check for changes or additions.
#
# Tips in this file have been contributed by Zachary Beane, Mo Oishi,
# Raphael Quinet, Sven Neumann, Carey Bunks and other people on the
# gimp mailing lists and newsgroup (comp.graphics
On Wed, 3 May 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Tue, May 02, 2000 at 08:15:44PM +0200, Raphael Quinet [EMAIL PROTECTED] wrote:
I tried to use the Perl-Fu scripts in 1.1.21 and I saw that all of
them abort with the following error displayed on the console:
** ERROR
I frequenty install the latest version of the Gimp on several
multi-user systems (Solaris and Linux). One thing that is frequently
reported by new users is that it takes a long time to start the Gimp
for the first time. I explain that it has to query all plug-ins once,
which is slow because of
On Tue, 2 May 2000, Pierre Rochefort [EMAIL PROTECTED] wrote:
I got the sources out of CVS and tried to compile. I have Glib 1.2.6
installed and it used to work fine (up until this morning). Has the
requirement changed in regards to Glib?
Yes. The current version of the Gimp requires
Oops! I forgot the second part of my patch. The problem with SA_NOMASK is
also present in app/main.c:
--- app/main.c~ Mon May 1 19:43:09 2000
+++ app/main.c Tue May 2 17:49:05 2000
@@ -334,15 +334,15 @@
/* Handle some signals */
- gimp_signal_private (SIGHUP, on_signal,
I just downloaded 1.1.21 and I tried to compile it under Solaris. The
build breaks early while compiling libgimp, with the following error:
gimp.c: In function `gimp_main':
gimp.c:202: `SA_NOMASK' undeclared (first use in this function)
gimp.c:202: (Each undeclared identifier is reported only
I tried to use the Perl-Fu scripts in 1.1.21 and I saw that all of
them abort with the following error displayed on the console:
** ERROR (recursed) **: could not find handler for message: 65536
aborting...
And this message is displayed in a pop-up box:
[/path/to/script]: the gimp is
On Wed, 26 Apr 2000, Michael Natterer wrote:
[...]
So the best thing is probably to remove install_cmap from gimprc and
have only a min_colors options.
But don't we have to tell plugins if the Gimp app installed a colormap?
Or can we leave this decision to the plugin's GdkRGB instance?
On Sat, 15 Apr 2000, [EMAIL PROTECTED] (Guillermo S. Romero / Familia Romero) wrote:
[...]
Regarding what Sven said about this taking too much memory, i think
that there are _a lot_ more users using the Gimp for small images
(like web things etc.), and so perhaps Gimp should be tailored to
On Mon, 17 Apr 2000, "Matthew Luchak" [EMAIL PROTECTED] wrote:
You might think this a lazy question but I can't find any info on a WBMP
plug-in for The Gimp - perhaps I'm blind.
Hopefully this can restore your vision:
http://registry.gimp.org/detailview.phtml?plugin=wbmp
-Raphael
On Thu, 6 Apr 2000, "William L. Sebok" [EMAIL PROTECTED] wrote:
Marc Lehmann [EMAIL PROTECTED] says:
The problem is that gettext itself does the detection (and so the only
solutioon would be to rpelace the gettext.m4 macros by our own versions).
I only get the results.
You mean the gnu
I just saw that Austin Donnelly has filed a bug report (#8312)
about the fact that the tips file is outdated.
Two months ago (Fri, 18 Feb 2000), I posted a message to this list,
suggesting some cleanups and pointing out the tips that are obviously
obsolete. Earlier on the same day, there was a
On Sun, 2 Apr 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
[...]
Unless somebody comes up with a better solution, I'll try the following
(Without any understanding of what I do):
if @MSGFMT@ is != "" and != "no" then just assume MSGFMT is valid, and that
msgmerge is somewhere in the path.
Yesterday, I downloaded and installed 1.1.19 on a "clean" system. I
found a number of bugs and I just reported them to the bug tracker.
Here is the list, in order to avoid duplicate bug reports and more
frustrations for those who are not aware of these bugs:
- #8148: gimp cannot be built because
On Wed, 29 Mar 2000, Federico Mena Quintero [EMAIL PROTECTED] wrote:
This should really use a CORBA interface and register some sort of
singleton factory object for images or other GIMP services.
(Look at how singleton applications work in GNOME; the Midnight
Commander or the Panel are good
On Fri, 24 Mar 2000, "Ben Fowler" [EMAIL PROTECTED] wrote:
[...]
On my machine, I have gimp-1.1.15. If I choose to update it,
I need a patch 1.1.15 - current level.
So far as I can tell, only patches for
previous level - current level
are archived.
I'm not sure that it would make
On Sun, 19 Mar 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Mon, Mar 13, 2000 at 05:01:56PM +0100, Raphael Quinet [EMAIL PROTECTED] wrote:
[...]
So the current situation is: if you do not install the required Perl
modules (especially Gtk.pm), most of the scripts do not produce any
useful
On Tue, 14 Mar 2000, FUJITA Yuji [EMAIL PROTECTED] wrote:
1. Does anyone know what "fu" is ?
I mean "script-fu", "perl-fu" or some kind of these names.
I think that it was a pun on "kung-fu". Not sure, though.
2. What is the biggest barriar to support 16bit depth in the GIMP ?
On Tue, 14 Mar 2000, Robert L Krawitz [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] (Raphael Quinet)
Yup! I have an elf-based Solaris system that does not know anything
about ldconfig... :-)
It's happened with at least 1.1.17 and 1.1.18. The fact that you're
using
On Tue, 14 Mar 2000, Simon Budig [EMAIL PROTECTED] wrote:
Marc Lehmann ([EMAIL PROTECTED]) wrote:
This might work for python, but it will not work for perl. It will find
the first perl in your path (which is often perl4), not the perl gimp
was configured with.
Are there really multiple
On Sat, 11 Mar 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
I just wanted to note that the suggestion of Raphael is based on
assumptions that were either never true, or were true many months ago.
Before all of you second his suggestions I would really appreciate it if
people looked at the
On Sun, 12 Mar 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Wed, Mar 08, 2000 at 07:23:49AM -0500, Robert L Krawitz [EMAIL PROTECTED] wrote:
1. libtool should make sure that the libraries are found anyway (unless
moved). ld.so.cache is only that, a cache
Well, then gimp.m4
I just uploaded the second part of my gimp_edit_fill patches to
ftp.gimp.org. As soon as it is moved out of the incoming directory,
you should be able to get it as gimp-quinet-000310-0.patch. This
second part fixes the Script-Fu scripts so that they are compatible
with the new interface to
Does it make sense to keep on using the version number (1.0, 1.1) in
the path for the $prefix/lib directory when it is not used for the
files in the $prefix/share directory?
Currently, all (binary) plug-ins and modules are stored in the
directory $prefix/lib/gimp/1.1/plug-ins (which should
I just uploaded a new patch to ftp.gimp.org (the file name is
gimp-quinet-000308-0.patch.gz). This patch fixes the problems with
Edit/Fill by allowing the user to choose the fill mode. The "Fill
with background color" is prefered by some users who have been using
the Gimp for a long time, but
This has been suggested before, but I would like to bring it up
again... I think that it would be better to disable the installation
of all Perl-Fu scripts if any of the required modules (Gtk, PDL,
Data::Dumper, Parse::RecDescent) are not detected by the configure
script or, more exactly, by
On Wed, 8 Mar 2000, Seth Burgess [EMAIL PROTECTED] wrote:
On Wed, Mar 08, 2000 at 01:07:52PM +0100, Raphael Quinet wrote:
This has been suggested before, but I would like to bring it up
again... I think that it would be better to disable the installation
of all Perl-Fu scripts if any
On Tue, 22 Feb 2000, [EMAIL PROTECTED] wrote:
On 22 Feb, Manish Singh wrote:
True, although we have a couple other inconsistencies already. The
coding style needs to be the same as the rest of gimp though.
I tried to bring it as near as possible. Of course a lot things could
be
By some sort of strange coincidence, I was in the process of cleaning
up the file gimp_tips.txt, when I saw the message from Ar't suggesting
to update that file.
Well, here are some tips that I would like to remove from gimp_tips.txt:
: When trying to save files as GIF, XPM, or any other
Is there any current archive for the Gimp mailing lists?
All links given the www.gimp.org page are dead and should probably be
removed (this also applies to the gtk-list).
I have unsubscribed myself from the gimp-users list some time ago and
I wanted to have a look at the current traffic before
On Wed, 16 Feb 2000, Glyph Lefkowitz [EMAIL PROTECTED] wrote:
Why are you bothering to change this behavior (edit/fill) when it makes
sense to 1/2 of the people who use GIMP, it's a historical precedent in
terms of the UI, and it's a huge amount of work to get to function
correctly? Are
I received several replies to my opinion poll, by private e-mail or
on this list. Here is a summary of what I got so far:
About changing the scripts that call gimp-edit-fill without setting
the colors first (thus taking the current color in use):
A1) No change to the scripts (they would then
On Wed, 16 Feb 2000, "Tony Webster" [EMAIL PROTECTED] wrote:
During the make process on my Mandrake Linux 7.0 machine of Gimp
1.1.17 I received the following error.
Running Mkbootstrap for Gimp::Lib ()
chmod 644 Lib.bs
LD_RUN_PATH="/usr/local/lib" cc -o ../blib/arch/auto/Gimp/Lib/Lib.so
Yesterday evening, I started to edit the Script-Fu scripts so that
they fill with the foreground color instead of the background color.
There are 215 calls to gimp-edit-fill in the scripts delivered with
Gimp 1.1.17, and most of them are preceded by a call to
gimp-palette-set-background, which
On Wed, 16 Feb 2000, Sven Neumann [EMAIL PROTECTED] wrote:
[...]
B2) Add a "flatten image?" option in all scripts, with the default
value set to TRUE.
B3) Add a "flatten image?" option in all scripts, with the default
value set to FALSE.
B4) Remove all calls to
On Fri, 11 Feb 2000, Sven Neumann [EMAIL PROTECTED] wrote:
Your list looked interesting. But, you seem to ignore the menu problem.
IMHO 2 columns is the absolute minimum since even then get problems with
the Help menu. If we'd allow less than 2 columns, not even Xtns will be
accesible any
On Thu, 10 Feb 2000, Nick Lamb [EMAIL PROTECTED] wrote:
On Thu, Feb 10, 2000 at 04:47:48AM +0100, Marc Lehmann wrote:
c) you gave _no_ reason why?
Ah, that wasn't clear from my diagrams? GTK+ draws space either side of
a menu item, so the Help menu can cover over Xtns, making it useless
Here is an interesting experiment for those who do not understand
what the problem is with the "Help" item in the toolbox:
- start Gimp
- resize the toolbox so that all tools are on a single column
(approx. 30 x 750 pixels)
- try to open a new image, or to do anything useful
The problem is
On Thu, 10 Feb 2000, "Daniele Medri" [EMAIL PROTECTED] wrote:
about Toolbox resizeble.
Flexibility is ok.. but some time create problems.
Why don't set fixed sizes x*y to cover all the dimension of toolbar?
This could be usefull to have right dimension and good rappresentation.
On Sat, 12 Feb 2000, Jon Winters [EMAIL PROTECTED] wrote:
^
You seem to have a problem with the date on your computer. :-)
I've had problems with the toolbox ever since it became re-sizable. I can
size it exactly the way I want it, three vertical rows of tools with
On Tue, 01 Feb 2000, Kelly Lynn Martin [EMAIL PROTECTED] wrote:
GNOME claims GIMP as part of GNOME because GIMP is better than any of
the existing GNOME apps. They're trying to piggyback on our success.
Personally, I think this is odious, but hey...
This statement is ridiculous. They are
On Thu, 03 Feb 2000, Kelly Lynn Martin [EMAIL PROTECTED] wrote:
On Thu, 3 Feb 2000 19:33:31 +0100 (CET), [EMAIL PROTECTED] said:
If you have a shared maschine the best would be to let the
administrator choose how much memory each user will get because
users'll ALWAYS try to get what they can
On Fri, 4 Feb 2000 (late at night), Marc Lehmann [EMAIL PROTECTED] wrote
On Fri, Feb 04, 2000 at 12:48:50AM +0100, [EMAIL PROTECTED] wrote:
Since the menus were reorganized I am constantly guessing wether
"Repeat Last" will repeat my last action, the one before or not work
at all, since
On Tue, 25 Jan 2000, Marc Lehmann [EMAIL PROTECTED] wrote:
On Mon, Jan 24, 2000 at 11:05:35AM -0500, Glyph Lefkowitz [EMAIL PROTECTED]
wrote:
Since the only advantage of this is the stack-trace for non-developers,
The consensus was to remove it in release versions. So if the only advantage
On Thu, 13 Jan 2000, "Garry R. Osgood" [EMAIL PROTECTED] wrote:
The latest is very good too, but the bristles are pointing the wrong way
(they would point *into* the ink blot as the brush pushes to the left).
I guess this bothers my boring and literal mind.
Good catch! Actually, it is even
I just had an idea: the lightbulb image that is used in File/About
could also be updated because it has not changed much since the early
days. So what about this: we use the image version 1.14 for the
splash screen (or 1.15 if Tigert can improve it), and the version 1.4
with the baloon for the
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, 21 Dec 1999, Marc Lehmann [EMAIL PROTECTED] wrote:
On Tue, Dec 21, 1999 at 10:56:28AM +0100, "Paul E.C. Melis" [EMAIL PROTECTED]
wrote:
Default for images could then be that there's no specific active tool,
while you could still select one (and make it active) later, if you want.
On Wed, 24 Nov 1999, Marc Lehmann [EMAIL PROTECTED] wrote:
On Wed, Nov 24, 1999 at 12:13:56AM +0100, Raphael Quinet [EMAIL PROTECTED] wrote:
How to make these scripts undo-aware? The problem is not really
I'd say the obvious way would be to make gimp_undo_push_group_start just
"
On Sun, 10 Oct 1999, Federico Mena Quintero [EMAIL PROTECTED] wrote:
[quoting Jay Cox]
If we unlink the swap file after opening it then we have no way of
knowing how much space gimp is using for it's swap file.
lseek() returns the offset to which you seeked, so lseek (swap_fd, 0,
89 matches
Mail list logo
