Andrei Simion wrote:
> Irek Słonina wrote:
>> /usr/bin/gimp -c -i -s -b '(plug-in-script-fu-server 1 10008
>> \"/tmp/gimpserverlog\")' '(gimp-quit 1)' 1>/tmp/gimprunlog
>> 2>/tmp/gimperrlog &
>>
>> Maybe try --display :1.0 -c -s, without no-interface.
>
>
> Thanks Irek, I'll try your comm
> And... it is buggy. It failed me when applying 256 color palette to a
> 256 colro image with the message:
> ---
> Error while executing
> (tiny-fu-set-cmap 6 12 "Gold")
>
> Error: car: argument 1 must be: pair
> --
> Not to mention:
>
> WARNING: Plug-In "tiny-fu"
> (/usr/local/lib/gimp/2.0/plug
Alan Horkan wrote:
It should call 'gimp_image_set_colormap' instead!
Normally I'd be in favour of expanding abbreviations to make things
clearer but in this case the shorter deprecated name avoids the confusion
caused by the American mispelling of Colour (damned Webster and his
patriotic
Hi,
If I do:
- Acquire
- Screenshot
- the sectected region
The plugin crash with a popup :
Plud-in crashed: "screenshot"
I've in the xterm from when I launched gimp:
The program 'screenshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAcces
Hi,
There are lots of Summer project sized tasks around the GIMP that we
could propose to Google. As a start:
- Add text boxes to the text tool
- Write a heal tool and an intelligent eraser tool (sharing as much
code as possible between them)
- Work on a framework to make plug-in settings
Dave Neary wrote:
> Should we make the proposals?
Doing this means that somebody is going to have to invest quite
substantial energy in evaluating candidates, defining a specific
project, handholding during the project, and evaluating the results.
The only people capable of doing this, realisti
Jean-Luc Coulon wrote:
> The plugin crash with a popup :
> Plud-in crashed: "screenshot"
I get the same result. Looking at the man pages, this apparently happens
if the key being grabbed has already been grabbed by something else --
but there does not seem to be any way to tell whether a given
William Skaggs ([EMAIL PROTECTED]) wrote:
> Jean-Luc Coulon wrote:
> > The plugin crash with a popup :
> > Plud-in crashed: "screenshot"
>
> I get the same result. Looking at the man pages, this apparently happens
> if the key being grabbed has already been grabbed by something else --
> but th
Simon Budig wrote:
> If XGrabKey might fail you can wrap it similiar to this:
>
> gdk_error_trap_push ();
> XGrabKey (GDK_DISPLAY_XDISPLAY (data->display),
>data->hot_keycode,
>AnyModifier,
>GDK_WINDOW_XWINDOW (data->root),
>TRUE,
>Grab
Hi,
[EMAIL PROTECTED] (2005-06-02 at 1841.46 +0200):
> - Write a heal tool and an intelligent eraser tool (sharing as much
> code as possible between them)
Algorithm is out there. :]
> - Reverse engineer PSD format for PS 10 and write the load/save
> plug-in (or adapt the existing one) to i
Hi,
Kevin Cozens <[EMAIL PROTECTED]> writes:
> Being one of those people who includes the 'u' makes me think I'm
> better off leaving my script functions using cmap instead of
> colormap/colourmap.
I think you should stick as closely to the GIMP API as possible and
use colormap instead of an amb
Dave Neary wrote:
- Reverse engineer PSD format for PS 10 and write the load/save plug-in
(or adapt the existing one) to it
Photoshop is up to version ten now?? Bloody hell... and I remember
when we felt all clever for figuring out some of the new PS4 PSD
features...
--adam
--
Adam D. Moss
Hi,
Dave Neary wrote:
- Reverse engineer PSD format for PS 10 and write the
load/save plug-in (or adapt the existing one) to it
Photoshop is up to version ten now?? Bloody hell... and I remember
when we felt all clever for figuring out some of the new PS4 PSD
features...
I'm gue
On Thu, 2005-06-02 at 18:41 +0200, Dave Neary wrote:
> Hi,
>
> There are lots of Summer project sized tasks around the GIMP that we
> could propose to Google. As a start:
>
...
> - Work on a framework to make plug-in settings saveable across
> sessions (this might be done now, is it?)
Persis
14 matches
Mail list logo
