0> In article <1269213446.26644.17.ca...@bender>,
0> Sven Neumann mailto:s...@gimp.org> ("Sven") wrote:
Sven> Given the fact that there are free (as in Open Source) PDF viewers
Sven> available,
On all our platforms? I doubt there's Xpdf or Evince for Macintosh and
Windows platforms...
Sven> I
same selected foreground colour, you can run
the script on many images. Here's the script-fu:
cut here ---
; whitebalance.scm
; adjust image white balance based on current foreground color.
; Author: Toby Speight <[EMAIL PROTECTED]>
; Licence terms: GNU GPL v2 or later
(script-fu
0> In article <[EMAIL PROTECTED]>,
0> Jasper Schalken mailto:[EMAIL PROTECTED]> ("Jasper") wrote:
Jasper> ... blurring an image with the blur tool in 2.3.15 darkens it
Jasper> as well as blurs, ...
Sounds suspiciously like an accumulation of rounding down in integer
arithmetic... anyone?
0> In article <[EMAIL PROTECTED]>,
0> Roel Schroeven mailto:[EMAIL PROTECTED]> ("Roel") wrote:
Roel> Sven Neumann schreef:
>>
>> GIMP doesn't rely on the mouse wheel for anything. It uses it if it's
>> there and that's what the mouse wheel controller is doing. Carol is
>> making a fuss out of not
0> In article <[EMAIL PROTECTED]>,
0> Des mailto:[EMAIL PROTECTED]> ("Des") wrote:
Des> The users are mark inclusions that they analyze on a stone. The
Des> three views are used as follows:
Des>
Des> 1 view serves as a working view or scratch pad
Des> 1 view serves as a view that will be printed
0> In article <[EMAIL PROTECTED]>,
0> Sven Neumann mailto:[EMAIL PROTECTED]> ("Sven") wrote:
Sven> On Thu, 2006-08-10 at 14:36 +0100, Toby Speight wrote:
>> I'm playing around with my plug-in build system at the moment,
>> tidying up the automake/au
I'm playing around with my plug-in build system at the moment, tidying
up the automake/autoconf stuff as I go (and as I learn about autotools -
I'm a newbie there). One thing I do is find the Gimp plug-in directory
like so:
/
| GIMP_LIBDIR=`$PKG_CONFIG --define-variable=prefix='DESTDIR' \
0> In article <[EMAIL PROTECTED]>,
0> saulgoode mailto:[EMAIL PROTECTED]> ("saulgoode") wrote:
saulgoode> 2. In a couple of places I employed the term "selection
saulgoode>frame" in order to differentiate operations that affected the
saulgoode>selection mask versus those that affected the
0> In article <[EMAIL PROTECTED]>,
0> Alexander Rabtchevich mailto:[EMAIL PROTECTED]> ("AR") wrote:
AR> 2. the hand in select by colour tool looks "spreaded" and isn't
AR>recognizable too.
I was going to mention this. The one for the smudge tool is good, and
a fairly natural shade of pink[1]
0> In article <[EMAIL PROTECTED]>,
0> Sven Neumann mailto:[EMAIL PROTECTED]> ("Sven") wrote:
Sven> On Wed, 2006-06-07 at 17:36 +0100, Toby Speight wrote:
>> While we're on this subject - obviously the plug-in process has no
>> chance to clear up if it
0> In article <[EMAIL PROTECTED]>,
0> Nathan Summers mailto:[EMAIL PROTECTED]> ("Nathan") wrote:
Nathan> "Cancelling" a plugin kills it unconditionally. It's been a
Nathan> few months since I looked at that code, but I'm fairly sure
Nathan> that there is no way for a plug-in to catch that it's be
(Delurk: I'm a sporadic developer of plugins, some of which are almost
good enough to shove in the registry, and I've watched this list for a
few months)
One of my current projects is a multifrequency blend tool (inspired
by, but not based on, the enblend program), and as part of its
operation, it
0> In article <[EMAIL PROTECTED]>,
0> Simon Budig mailto:[EMAIL PROTECTED]> ("Simon") wrote:
Simon> Better have an undiscoverable workflow-optimization than an
Simon> undiscoverable feature.
One way to make it discoverable is to display a hint in the New Layer
dialog window. (This might be condi
13 matches
Mail list logo
