Re: Hi, I'm here to scratch a scripting itch.

> you may want to invlove yourself in development of gimp 1.4 or 2.0 if you > really want to make really big changes. That's right. We won't accept any changes for Gimp-1.2 unless its an obvious bugfix and I'd even agree to declare the batchmode officially broken and release 1.2 before we do maj

Re: Bug reports

Hi, > Can someone close the following bugs? I have reported this twice to > [EMAIL PROTECTED], but no one closed them. > #12303, #12302, #12298 Wouldn't it be easier to close them yourself instead of asking other people? Especially since closing them is simpler and less work. You should read ht

Re: How many layers are supported?

> >I need this information to beat a Photoshop-user. > > That would probably depend on the layer size, how much memory you've got, and a > gazillion of factors. If you mean the theoretical max, I'd guess that's as many > as your int size supports (ie. about 2 billion for a 32-bit machine), withou

Re: Perl Scripting

Hi, > Perl normally should be there. But since the Perl plugin has never > really worked (greetings Marc! :) it's not a big phenomenon that > it doesn't work for you... Sorry Daniel, but don't we don't need that kind of FUD here. If gimp-perl is still not working for you, please let us know

Re: GIMP Table Magic

Hi, first of all: please stop posting HTML mail to this list. > I was looking in the DB Browser, and noticed a function called = > file-GTM-save. In the blurb, it says that it is called "GIMP Table = > Magic", and it creates an HTML table from an image by slicing it up. = > This is not unlike wh

Re: Help files

Hi, > > Format issue 1: DocBook or HTML? > > > > > Points in favour of DocBook: > > * Can be pushed to a variety of output formats with existing tools. > > * Is more searchable and indexable and whatnot, using hypothetcial > > tools. (If you can point to

libgimp COMPAT_CRUFT now disabled by default

Hi, in a final move to finish the 1.2 libgimp API we have changed the logic of the COMPAT_CRUFT definitions in libgimp. The compatibility definitions from gimpcompat.h and gimpenums.h are no longer included by default. Old plug-ins that use the 1.0 API will therefore not compile against the 1.2

Re: [Gimp-print-devel] libgimp COMPAT_CRUFT now disabled by default

Hi, > Are you not cleaning up CAN_HANDLE_INDEXED and friends? you are right, we should have done this earlier. I've done it now. Salut, Sven

Re: api break before release

Hi, > While, in theory, I agree that having compatibility cruft inside a > software package is bad, I think breaking compatibility deep within a > feature freeze was a very bad idea. > > I thought different this afternoon when I could just enable > GIMP_COMPAT_CRUFT_STH, but it just turned out t

Re: resource management...

Hi, > Secondly, I'm confused by the function gimp-file-save. Specifically why do > I need to pass an image and a drawable? If I load an image, do some image > level manipulations on it, and then want to save it with gimp-image-save, > do I need to create a layer? most save plug-ins can not

Re: api break before release

Hi, >Are you sure? Why does it work for the gimp-print plug-in then? > > We've been using the old names. I ran Sven's conversion script to > generate the new names, and put a whole stack of #define's in the one > UI-related file that's shared between the 1.0 code and the 1.2 code. > > It d

Re: api break before release

Hi, > Maybe it's just gimp-perl then. Maybe it's the fact that gimp-perl simply > relies on all symbols, while gimp-print probably only relies on the most > common (&small) subset. In that case, most probably only gimp-perl is hurt... > Which might also be the only plug-in where the community has

Re: Icon of color picker

Hi, COUTIER Eric <[EMAIL PROTECTED]> writes: > After Tobias Gärder message, i've tried to use color picker on the image and > i've seen a little "bug" (it isn't really in fact) with the mouse cursor: > when the mouse fly over transparent zone, the cursor become "pipette with > forbidden panel".

Re: Gimp gimp-1.1.28 (script-fu problem)

Hi, Jeff Sheffield <[EMAIL PROTECTED]> writes: > [jsheffie@kelly bin]$ ./gimp > ^[[A./gimp terminated: Interrupt > /opt/gimp/gimp-1.1.28/lib/gimp/1.1/plug-ins/animate_cells terminated: > Interrupt > --- > animate_cells...?? animate_cells is a gimp-perl script, which makes me think t

Re: [patch] Wishlist #7100 (create layer mask with layer as content)

Hi, Andreas Jaekel <[EMAIL PROTECTED]> writes: > I have just patched gimp-1.1.28 so that it now can do > what is registered as wish list item #7100 > #7100: [Wishlist] layer mask initialization > in the bug database. (meaning, you can create a new > layer mask and initialize it with a (desatur

Re: Pb with the display of the Gimp Toolbox (1.1.28)

Ludovic Poitou <[EMAIL PROTECTED]> writes: > I'm facing a pb with the way the toolbox is displayed. I've had this pb > with the 1.1 versions, and it's still there (1.1.28). Just to make sure: Have you tried to remove the file ~/.gimp-1.1/sessionrc? Please report back if this helps or if the pro

Re: exec-prefic in systemwide gimprc

Hi, Sascha Luedecke <[EMAIL PROTECTED]> writes: > I have a multiplatform installation of gimp. Though one can specify > --prefix and --exec-prefix to configure the sources and thus the > installation, the separation is not 100% clean. > > The file > > /etc/gimp/1.1/gimprc > > contai

Re: [gimpwin-users] gtkrc

Hi, Tor Lillqvist <[EMAIL PROTECTED]> writes: > It used to be posssible to have a user-specific gtkrc file for GIMP, > in the user's .gimp1.1 directory (_gimp1.1 on Windows), but apparently > this has changed at some time. (I had not noticed.) The user-specific > gtkrc file that user_install (.b

Re: build problems from cvs

Marc Lehmann <[EMAIL PROTECTED]> writes: > On Fri, Nov 03, 2000 at 08:12:07AM +0100, Marc Lehmann <[EMAIL PROTECTED]> wrote: > > Since quite some time I get spurious errors while building gimp: > > sorry, found it (I am not sure that is, I just checked out the build module > in gnome and moved i

Re: GIMP help docs

[EMAIL PROTECTED] writes: > This is now the case: The help is completely converted now and we found > a way to compile it very nicely. We just need to integrate it now and get > Sven to add some of the promised new and necessary features to the helpbrowser. If you want me to change the helpbr

Re: Gimp tool icons

Zolan Davis <[EMAIL PROTECTED]> writes: > It isn't urgent but this seemed the best place to ask. If not, please provide >alternative. > > Please tell me the rationale behind having the drawing icons point downwards. > > On my desk, the monitor is above the mouse, and my other applications refl

Re: GIMP help docs

Hi, [EMAIL PROTECTED] (Raphael Quinet) writes: > Hmmm... Looks like we need a couple more beta releases before 1.2. ;-) Nope, the new help system will most probably be integrated after 1.2.0 was released. There's no point in waiting any longer. > But I am wondering... What's the point in ma

Re: signal handler problems in screenshot plug-in

Hi, [EMAIL PROTECTED] (Raphael Quinet) writes: > I took a look at bug #27786 "screenshot plugin on Solaris takes bus > error on exit" because I wanted to see if I could reproduce it. Well, > I got another problem: the screenshot plug-in exits with "xwd didn't > work" before giving any results.

Re: blury picture

robert lund <[EMAIL PROTECTED]> writes: > I AM NEW TO THIS KINDA. I AM MAKING A SHIP FOR A GAME CALLED XSHIPWARS WHICH > REQUIRES A ROTATION OF THE PIC 22.5 DEGREES UNTILL IT GOES ALL THE WAY > AROUND TO 360 SO YOU END UP WITH 16 PICS OF THE SAME SHIP BUT JUST IN A > DIFFERENT POSITION. MY PRO

Re: [PATCH] Gimp-Print locale

Zbigniew Chyla <[EMAIL PROTECTED]> writes: > Gimp-Print uses non-existant textdomain. Attached patch fixes this. Is it OK > to commit? > > > Zbigniew > --- gimp/plug-ins/print/print.c.cyba Tue Nov 14 19:29:01 2000 > +++ gimp/plug-ins/print/print.c Tue Nov 14 19:25:06 2000 > @@ -327,7 +32

Re: [newbie] 1.1.29 build problem

Mats Nygren <[EMAIL PROTECTED]> writes: > Probably this is the wrong place but I know no other. > > Having downloaded the gimp and built it the following message > is written several times at startup: > > Gtk-WARNING **: Unable to locate loadable module in module_path: > "libpixmap.so", This

Re: layer_get_offests(layerId, &x, &y);

Maneesh Yadav <[EMAIL PROTECTED]> writes: > No one knows how to get the offsets for a layer from libgimp do they? Yes, we know. Since a layer is only a special kind of drawable, the following call will perfectly do: gboolean gimp_drawable_offsets (gint32 drawable_ID,

Re: use of the Delete key on Dec keyboard or similar

Olivier Lecarme <[EMAIL PROTECTED]> writes: > Now you only need to get them Gimp developers to make it so :). (I'm not > a real full-time developer, I'm just on the list because I fixed a bug > not so long ago) GIMP does not do anything about key mappings and it will never do. Configure your X-

Re: [PATCH] improving on i18n

Zbigniew Chyla <[EMAIL PROTECTED]> writes: > As you probably already know there are lots of problems with current i18n > tools. Every genuine inscription can have only one equivalent in particular > language when using gettext. In the case of GIMP this is really serious > problem because of huge

Re: [PATCH] improving on i18n

Hi, Zbigniew Chyla <[EMAIL PROTECTED]> writes: > On Tue, 2000-12-05 at 16:01:17, Sven Neumann wrote: > > > Probably a good idea, but I doubt we can count this as a bugfix. We > > should consider integrating a fix like this after the 1.2 release. > > This p

Re: [PATCH] improving on i18n

Zbigniew Chyla <[EMAIL PROTECTED]> writes: > This patch _fixes_ GIMP translations. Currently it's _impossible_ to > correctly translate GIMP to any slavic language (and probably many others). > Polish GIMP users keep saying "Can you speak Polish? Translation is broken!" > and the only thing we

Re: 1.2 and beyond

Hi, Robert L Krawitz <[EMAIL PROTECTED]> writes: > What are the plans for maintenance of 1.2? At some point (long before > 1.4), we're going to do a gimp-print 4.2; it may even happen in 3 > months or so if the quality (particularly color) improvements outrun > the rest of the development proje

Re: How much longer do I have to put up with this shit? (This is NOT a troll)

Hi, Zachary Beane <[EMAIL PROTECTED]> writes: > On Mon, Dec 11, 2000 at 02:31:13AM +0900, [EMAIL PROTECTED] wrote: > > > * Contents of about half of the dialog boxes seems to be entries in a > > contest for the next century's ugliest user inteface. What ever > > happened to uniform interfa

Re: [Sven Neumann] Assistance with GUI design

[EMAIL PROTECTED] writes: > I am rather shocked. For someone who doesn't really know me, that's some > pretty bold statements. But then again, I've come to expect that from > you, dear Sven, so I don't really take it too seriously. You are still > upset from when I called you an asshole about

Re: [nick lamb] UI again

[EMAIL PROTECTED] writes: > Hey, that's -YOUR- window key. Throughout this thread I felt like I was > always being talked down because these are -MY- ideas. Nobody wants to > hear them because they are -PERSONAL- and -YOU- don't -LIKE- > them. Instead, why not make things like that configurabl

Re: RFC: The future of The GIMP

Hi, Tino Schwarze <[EMAIL PROTECTED]> writes: > Why would you want to reinvent the wheel? Follow Unix philosophy: Use > tools which are already there. > > I propose: > 1. let the user use the package tool she wants > 2. make plugins relocateable (I guess, not only RPM can do that) > 3. provide

Re: RFC: The future of The GIMP

Hi, Jon Winters <[EMAIL PROTECTED]> writes: > We should keep in mind that the vast majority of Gimp users are not > compiling from source. A shell script is not something those folks > understand. Their reaction will be... Heh.. Where are all the plugins, > this sucks! Please keep in mind tha

Re: RFC: The future of The GIMP

Hi, Lourens Veen <[EMAIL PROTECTED]> writes: > All true, but then the problem is that non-technical users have to wait > for someone (or their favourite distribution) to package new plugins. > IE, let's say I write a new plugin, put it on plugins.gimp.org in source > form. Then Joe User can't us

Re: Request To Revert Curve Tool

Hi, David Hodson <[EMAIL PROTECTED]> writes: > After some offline discussion with Garry, we have jointly agreed > to propose the following (my wording, don't blame him): > > The curves and levels tools should reset when called, and this > behaviour should be reinstated before 1.2. > > Comments?

Re: gimp 1.1.31-32 BUG

[EMAIL PROTECTED] writes: > I have just downloaded 1.1.31 and 1.1.32 patches from ftp.gimp.org > > I notice that 'TODO' file has been updated to show some things that will > happen with Gimp. > > However, I don't see any mention of "improved keyboard operation", > i.e. the stuff that generated

Re: Problem building an gimp-1.1.32 RPM

Henning Sauer <[EMAIL PROTECTED]> writes: > today I tried to build a an rpm of gimp-1.1.32 from the source via > "rpm -ta gimp-1.1.32.tar.bz2", but it didn't work because in the > installation phase it couldn't find the gimp executable in the > /usr/bin directory under BuildRoot. Instead the gimp

Re: new plugin

Hi, david rohde <[EMAIL PROTECTED]> writes: > I am currently writing a new plugin, which I hope if there is intrest in it > could be included in to standard gimp distributions. I understand that the > gimp is frozen at the moment, but if anyone could tell me the process > required for a new plu

Re: Some Compile Error 1.1.30

Hi, Frank Werner <[EMAIL PROTECTED]> writes: > i have problems to compile gimp-1.1.30. > I have installed glib-1.3.2 and gtk+-1.3.2. > > Can someone tell me, how can I solve this problem? The INSTALL file clearly states that gimp-1.1.x will not compile with the developers versions of glib and

Re: GIMP 1.2.0 and IRIX

Hi, Albert Chin-A-Young <[EMAIL PROTECTED]> writes: > On IRIX 6.2 and 6.5 with GIMP 1.2.0: > > $ gimp > /opt/TWWfsw/gimp12/bin/gimp: Failed to load one of the brushes in the > brush pipe > "/opt/TWWfsw/gimp12/share/gimp/1.2/brushes/SketchBrush-64.gih" > /opt/TWWfsw/gimp12/bin/gimp: Wa

Re: GIMP 1.2.0 and IRIX

Hi, "Garry R. Osgood" <[EMAIL PROTECTED]> writes: > > I can successfully use pepper.gbr. File->Open loads it in just fine > > and I can select the brush in File->Dialogs->Brushes. > > > > FYI, I have no problems with Solaris 8/SPARC nor Tru64 UNIX 4.0D/5.0. > > Just this evening (GMT -5.00)

gimp translations, CVS branches

Hi Rodrigo, I noticed that you checked updates for the spanish translation of gimp into CVS. Please note that we branched gimp CVS after the 1.2.0 release. Since I assume you want the updates to go into the stable branch (so they are available with the upcoming 1.2.1 release), you should have c

Re: GIMP 1.2.0 and Solaris 7/SPARC

Hi, Tino Schwarze <[EMAIL PROTECTED]> writes: > Without having looked at the code - what do we need that many FDs for?! > We don't need to open all palettes at once, do we? Gimp-1.2.0 leaks a filedescriptor when loading palettes. This has been fixed in the meantime. Salut, Sven

Re: Suggestions for gimp

Hi, "Orson Jones" <[EMAIL PROTECTED]> writes: > Background Remover > Used for defringing. Makes an edge partialy transparent and > removes the background color from the semi-transparent area. > (Imagine a black area bluring onto a white background) > In this example the gray area would b

Re: Submitting Patches

Hi, "oliver" <[EMAIL PROTECTED]> writes: > I've hacked a few of photoshop's blending modes (dodge and burn -- which > are different in photoshop than multiply and divide -- and hardlight) into > the gimp 1.3 sources. I was wondering if this would make an interesting > patch, and if so how

Re: Submitting Patches

Hi, "oliver" <[EMAIL PROTECTED]> writes: > An updated version of the patch is attached. Let me know if all is well > this time. I have applied the patch to CVS. If you would have given us your full name, I would also have been able to it to the ChangeLog... Salut, Sven

Re: Histogram patch

Nick Lamb <[EMAIL PROTECTED]> writes: > A potential patch for the histogram tool in 1.2.x (assuming we do plan > to release e.g. file handle leak fix as a 1.2.1) has been uploaded > as gimp-ruth-010109-0.patch.gz The patch is available on ftp://ftp.gimp.org/pub/gimp/patches. Please give it a try

Re: gauss_rle bad error (indexed image)

Rick Bradley <[EMAIL PROTECTED]> writes: > I've run into a problem with gauss_rle and perl-called script-fu's in > Gimp 1.1.29. > > Basically: > > - I'm calling some of the various logo script-fu's using the perl > Gimp interface > > - On those script-fu's which internally use gauss_rle I ge

Re: Plugin patches

Jens Christian Restemeier <[EMAIL PROTECTED]> writes: > I recently got a bug report for QBist, and in turn made a new version. > What is the easiest way to get it into CVS-Gimp ? I made a patch, but > the patches directory on ftp.gimp.org doesn's seem to be cleaned for 2 > years, The patches dir

Re: plugins

Hi, Martin Weber <[EMAIL PROTECTED]> writes: > Could we now start and add new plugins to GIMP cvs? No, but we should settle on a system for plug-in development, maintainance and distribution and start to move plug-ins out of gimp CVS soon. Some ideas have come up, but the discussion calmed dow

Re: GIMP 1.3x - gradients

Hi, Martin Weber <[EMAIL PROTECTED]> writes: > We should change the behavior of the selection of gradients in gflare and > we should allow functions to be used as gradients in GIMP like random in > gflare. We accept patches (or properly outlined proposals). Salut, Sven

Re: Bug in configure

"Uwe Koloska" <[EMAIL PROTECTED]> writes: > "./configure --help" gives a wrong default for "--enable-gimpdir": > --enable-gimpdir=DIRchange default gimpdir from .gimp to DIR > must be > .gimp-1.2 > > Same change in INSTALL. (I don't kn

Re: configure

Martin Weber <[EMAIL PROTECTED]> writes: > There seems to be a problem in configure. If I use a freshly installed > Linux without the headers of the kernel sources installed, configure runs > without any error, but doesn't define certain variables. So the whole couldn't > compile. The thing is th

Re: problems with windows gimp

Hi, Nick Lamb <[EMAIL PROTECTED]> writes: > On Thu, Jan 18, 2001 at 12:42:23AM +0200, Tor Lillqvist wrote: > > (No, I don't know why duplicate PDB procedures cause strange errors > > and not just warnings. Anyway, GIMP seems to handle this situation > > better in the current gimp-1-2.) > > It's

Re: problem with gtk+ colorselector

Hi, "Uwe Koloska" <[EMAIL PROTECTED]> writes: > I have found a very annoying problem with gimps gtk+ colorselector. Since > I don't use it normally, it came into my eye after installing digipencil. > > Because the testprogramm that come with gtk+ shows the right behaviour, it > maybe there

Re: New wishlist for next GIMP available??

Hi, Avi Bercovich <[EMAIL PROTECTED]> writes: > has the wishlist for features for gimp 1.4/2.0 been started?? If so where > can I find it/add to it? The source tree contains a file TODO which is a collection of ideas that have come up over the years. Actually the file should not be called TODO,

Re: problem with gtk+ colorselector

Hi, "Uwe Koloska" <[EMAIL PROTECTED]> writes: > This isn't in sync with the behaviour of the other selectors. There you > always have the comparison with the color you want to change! If you click > on the fg-color you can watch your changes in contrast to the old color. > It's of very lim

Re: problem with gtk+ colorselector

Hi, Nick Lamb <[EMAIL PROTECTED]> writes: > On Sun, Feb 04, 2001 at 04:45:58AM +0100, Sven Neumann wrote: > > The colorselector has already undergone a major overhaul in the HEAD tree. > > The color previews as well as all sliders are now global to all color > >

Re: Proposal for a texture selector

Hi, "David A. Bartold" <[EMAIL PROTECTED]> writes: > There needs to be a way to select a texture before advanced tools can > be added to The GIMP. I propose to create a new dialog box similar > to the pattern selector. Instead of containing tilable RGB pixmaps, it > will contain tileable greys

Re: Proposal for a texture selector

Hi, "David A. Bartold" <[EMAIL PROTECTED]> writes: > Very cool, that should simplify the process of creating a texture selector > greatly. In addition to providing UI elements for the user, there also > needs to be an API for scripts and the plug-ins to change the texture. Thanks to Mitch the

Re: Gimp 1.3 compile and link dependencies

Hi, Hans Breuer <[EMAIL PROTECTED]> writes: > while adapting make and export definition files for the > win32 build of Gimp 1.3, there where some questions ariseing : > > - what are the supposed dependency between all the libgimp* > libraries ? you got it right in your graphics below. > wh

Re: gimp.themes.org ideas

Hi, Jordan Evatt <[EMAIL PROTECTED]> writes: > hey guys. we at themes.org are creating gimp.themes.org (you knew it was coming). i >was wondering if anyone had any suggestions or ideas for what should go on it. i just >got through talking to #gimp, and here's what i have so far: > > a) don't

Re: porting a plug-in from 1.18 to 1.20

Hi, david rohde <[EMAIL PROTECTED]> writes: > I have been trying to port a plug-in that I have been writing to the latest > gimp, but I have been having troubles. > > Firstly a lot of the constants that were defined in 1.18 are no longer defined > in 1.20 for example RGB. Is this a deliberate

Re: Proposed Paint Core changes to support textures

Hi, "David A. Bartold" <[EMAIL PROTECTED]> writes: > * new function gimp_context_get_texture: > Returns a GPattern * from the specified context. Heeding Seth's > advice not to create a new file format without good reason, I've > determined the .PAT format to be suitable for this p

Re: Proposed Paint Core changes to support textures

Hi, "David A. Bartold" <[EMAIL PROTECTED]> writes: > I think a better solution would be a definable pressure curve, much like > Wacom's Windows driver has. That'd probably be a feature of the > general mechanism you described and perhaps what you have in mind. A > user (or a brush designer) ca

Re: Proposed Paint Core changes to support textures

Hi, [EMAIL PROTECTED] writes: > > I think a better solution would be a definable pressure curve, much > > like Wacom's Windows driver has. That'd probably be a feature of the > > general mechanism you described and perhaps what you have in mind. > > Hm, generating a lookup table and getting

Re: ANNOUNCE: GDynText 1.5.4

Hi, Marco Lamberto <[EMAIL PROTECTED]> writes: > Now really compiles with GTK_DISABLE_COMPAT_H defined. > > I can download it at: > > or: > If you think this release containes some important

Re: Value in histogram

Hi, Nick Lamb <[EMAIL PROTECTED]> writes: > On Thu, Feb 08, 2001 at 01:36:10PM +0100, Roel Schroeven wrote: > > The value in the gimp histogram is calculated as the maximum of the red, > > green and blue channels now. Wouldn't it be better to use the average of the > > three color channels? > >

Re: [Fwd: Gimp/fourier]

Hi, [EMAIL PROTECTED] (Carsten Hammer) writes: > > gcc -g `gtk-config --cflags` -O2 -Wall -c fourier.c > > Anybody here who can help Frank? I dont know whats going on there.. what about using gimptool to get the compiler and linker flags right? Try: gimptool --build fourier.c or if t

Re: NLS-Problems passing GIMP_PDB_FLOAT PDB parameters

Hi, "wolfgang hofer" <[EMAIL PROTECTED]> writes: > - The Problem is related to NLS (the LANG Environment Variable) > (when I do unset LANG, everything is OK) If you had used the macros gimp provides for initializing I18N, you wouldn't have had this problem. Your code should look like this:

Re: Error messages from a plug-in

Hi, Ernst Lippe <[EMAIL PROTECTED]> writes: > What is the "official way" to display error messages from a plug-in to > the user? > Basically what I looked for was a simple window (perhaps even with some > threatening icon) that I could invoke with a single function call > (I guess that I have be

Re: CVS HEAD channel previews?

Hi, Nick Lamb <[EMAIL PROTECTED]> writes: > Maybe it's just me, but it seems that channel previews have been broken > in CVS HEAD for some time. I'm not complaining, it just seems possible > that no-one has bothered looking at that entire tab for say, two weeks > and didn't realise that they'd b

Re: Layers, dialogs and other bits of love on Valentines Day

Hi, Emmanuel Mwangi <[EMAIL PROTECTED]> writes: > Anyways, all that is far off. I was wondering you could just have nested > layers in this next version of Gimp. It doesn't even have to have all the > strange but, cool stuff that tigert was talking about but, even just being > able to organize

Re: Layers, dialogs and other bits of love on Valentines Day

Hi, "gimptek DESIGNS" <[EMAIL PROTECTED]> writes: > Maybe I wasn't clear. I didn't mean layering should change in any way than > it does now (except maybe adding Photoshop style color dodge ;) but, just > the representation of it should. The way the layers stack isn't the change > that I was t

Re: swap files

The following is not a real solution, but it I think it would make the user understand the necessary internals better: Add a second dialog to the "User Installation" process that explains the user Gimp's way of handling memory and allows him to choose the size of the tile-cache-size and the lo

Re: Which Save filters should be enabled?

> > The Export functionality slowly creeping into CVS Gimp is really nice, > but it leaves me with a dilemma somewhat related to my last set of > changes (ie fixing Save As... list of save formats) > > Should plug-ins which have working Export declare themselves capable of > all image formats fo

Re: Plugins

Hi, my EUR 0.02 to the plug-in discussion I don't think that internationalisation is our major problem with plug-ins right now. This doesn't mean that we shouldn't think about it now, but our main problem is the mass of plug-ins shipped with the Gimp. The Filters menu is IMHO overcrowded

Re: Script-Fu Error

Hi, > > "ERROR: unbound variable (errobj gimp-image-undo-disable) > > If this happens while running a logo script, > you might not have the font it wants installed on your system" > > As of tonight's CVS update, ever single script-fu script is doing this > when I attempt to execute any of them

Icons in L&C dialog (and elsewhere)

Hi, would somebody cry and whine if I check this in: http://sven.gimp.org/files/lc_new_icons.png IMHO a little facelift can't hurt and the anchor does fit better with the Gnome icons. Salut, Sven

Re: Icons in L&C dialog (and elsewhere)

Hi, Uh, Gimp users/developers are so conservative ... > I am not sure. Gimp is a drawing application and thus colors are important > part of the work being done. I kinda like the fact that the icons in the > gui are not colored. I dont know, what do others think? It wasn't the lack of colors th

Re: Icons in L&C dialog (and elsewhere)

Heh, this thread turns out to be some sort of Gimp-book authors meeting, so I should probably throw my Euro 0.02 in here... IMHO cleaning up the user interface is one of the most important things that have to be done after a feature freeze. See it like this: people have been throwing nifty fea

Re: grid plugin

Hi Xach, > The real-life units in the grid plugin are nice. > > However, removing the ability to a) start with a negative offset b) exceed > the image size and c) remember the last used unit have rendered this plugin > completely useless for what I usually use it for. > > Removing options jus

Re: grid plugin

Hi, > > > > I use it frequently to generate horizontal bars a few pixels apart. I don't > > want any vertical bars, so setting a -1 offset and making it image_width+2 > > spacing does the trick. > > It sounds to me like horizontal/vertical line checkboxes are called > for in this case. Maybe al

Re: BUGREPORT: Rotate doesnt work

> On Tue, Oct 26, 1999 at 12:32:24AM -0700, Tuomas Kuosmanen <[EMAIL PROTECTED]> wrote: > > > > Hello. > > > > The new dialog for the transform tool is very cool. However the Image -> > > Transforms -> [Image|Layer] -> Rotate doesnt seem to work..? Maybe > > something broke along the road? > >

Re: limited slider range

> > PS: I like having a slider better than a spinbutton on the ink tool because > you can slide it all the way to the max or min w/o having to incriment slowly > one-by-one (like with a spinner) > I don't like the idea to enlarge the ideas even more, but what from what I read from this thread I

Re: BUGREPORT: Rotate doesnt work

Hi, > > What additional information do you require?? > > See above. In script-fu it is probably: > > plug-in-rotate something image drawable 3 0 > Well, it seems that someone changed the calls to gimp_drawable_is_layer() in all plug-ins and forgot to change the PDB calls... Salut, Sven

Re: More Inconsistency in eraser, blur and dodge tools

Hi, > There are some major inconsistency or more precisely hard to use functions > in the eraser, the sharpen/blur and dodge/burn tools. > > Pressing Ctrl will change the tool behavior from eraser --> anti-eraser, > blur --> sharpen and dodge --> burn. > > Pressing Ctrl will in combination w

Tile Cache Size

Hi, Tigert wrote: > > Btw, can anyone explain what size should the tile-cache be? I have 256MB of > ram, and sometimes I need to work with 3000x3000 images, and I love to use > _lots_ of layers.. This can lead to horrible swapping that can kill X if it > goes too far. Is the tile-cache a sandbox

Re: Transform tool not ready for release

> I've been hacking at the internals of the transform tool, but until > now I hadn't looked at how it worked from the outside. It's just not > right! You need to be able to set the transform by swapping between > modes (rotate/shear/scale/perspective - plus move), adding to the > existing transfor

Freeze

Just my 2 cents: As I stated earlier, I'm against declaring a freeze that totally stops development and leaves the application in an inconsistent state. On the other hand I think that only a few inconstistencies are left now. Those can be figured out in a much shorter time then the release date

Help System

Hi, > Except it doesn't seem to work on systems without GtkXmHTML installed. I > don't have that on my systems Would it be possible for the build to recognize > this and remove the Help option from the File menu? The current dialog that > pops in these cases (no GtkXmHTML) is fairly confusing

Re: Help System

> > Consider that GtkXmHTML cannot be compiled on linux libc5 systems (or generally > systems without thread support) because it needs the threaded version of > strok() strtok_r(). The latter one is new in glibc2 (aka libc6) an for the > gnome system it is doubled in gnomesupport. So to make Gt

Re: i18n problem

> >In recent 1.1.11 or CVS Gimp, there is a problem with i18n. All not-translated > >menuitems show up as "File" (in their respective i18n equivalent). > > Is your translation table fr.po ? > It seems to be broken when I tried to "make update-po". > If it is, the german de.po is broken too, sin

Re: i18n problem

> >If it is, the german de.po is broken too, since I experience the same weird > >problem here. > > What menuitems are replaced by Datei? I could not reproduce the > problem. > As far as I can see all menu-items that are provided by plug-ins. Additionally the Dialogs entry in the image menu (no

Re: cause of the problem (problems with MPEG animations)

Hi, > > Now I download sources for mpeg.c and have found that plugin crashes after > > gimp_progress_update (1.0); > > on line 320. I am not specialist in GIMP sources but it seems to me that this > call invoked "for illustration only". Thus I comment this line. After this > GIMP loads mp

Re: i18n problem

> When I start gimp as follows: > > % env LANG=de_DE.ISO_8859-1 gimp > > I can see only 2 "Datei"s. "/Datei" and "/Datei". > No other "Datei"s ... > I just used LANG=de, but using LANG=de_DE.ISO_8859-1 doesn't change the behaviour here. Salut, Sven

  1   2   3   4   >