On Fri, Nov 01, 2002 at 05:11:42AM +, Nick Lamb wrote:
> * Image formats for X clipboard
>[User hits 'Edit/Cut' in Gimp and then 'Edit/Paste' in kWord]
Does GIMP use the X clipboard at all, BTW? I think the Windows version uses
its internal clipboard, at least (which is quite annoying :-)
On Thu, Oct 31, 2002 at 09:30:57PM +0200, Juhana Sadeharju wrote:
> Possible topics include:
> -Are there a need for Linux graphics standards
Standards which are arguably needed, off the top of my head:
* TWAIN-like aquisition standard (not SANE)
[How should my webcam software work with GIMP
Hi,
RW Hawkins <[EMAIL PROTECTED]> writes:
> True, 8 bit is OK for "animation" work (like Shrek) but for live
> action it just does not cut it. This is why film gimp supports 16
> bit. Any house doing live action work is likely long switched over to
> 16 bit.
>
> As a photographer my results are
True, 8 bit is OK for "animation" work (like Shrek) but for live action
it just does not cut it. This is why film gimp supports 16 bit. Any
house doing live action work is likely long switched over to 16 bit.
As a photographer my results are significantly better if I do scan and
initial level a
Just FYI (I have no specific goal with this mail ;): I met some guy from
Dreamworks ("Shrek") at the LWE in Frankfurt, and he told me that their
whole rendering infrastructure is 8 bit, including intermediate results
(so the whole of Shrek was done at 8 bits, with a later dynamic adjustment
of the
Hi,
Jeff Trefftzs <[EMAIL PROTECTED]> writes:
> > that menu entry points to layer_resize_to_image() in app/layers.c.
>
> Aha! I didn't see a reference to it in the PDB explorer, so I
> thought the perl-fu function was what was used. Should I file a bug
> report? At any rate, I couldn't find i
Announce:
I'm pleased to announce a new mailing list: linux-graphics-dev
at "http://music.columbia.edu/mailman/listinfo/linux-graphics-dev";.
It is a get-together list for open source, free graphics software
developers working in Linux.
The mailing list is convenietly also available in digested
Im desiging a small application, and I need some insipiration for an
undo system;its obvious that the GIMP's undo system, and the data it
operates on, is far more complex than that of a text editor, so i was
curious about what it's approach was.
Thanks for the assitance. Im no under any deadline
Hi,
Jeff Trefftzs <[EMAIL PROTECTED]> writes:
> > oh, come on. calling perl to resize the layer to the image size is a
> > bit of an overkill if it can also be done in one or two lines of
> > scheme. The following code is untested, but might actually work: ...
>
> It may be overkill, but it's av
Sven wrote:
> oh, come on. calling perl to resize the layer to the image size is a
> bit of an overkill if it can also be done in one or two lines of
> scheme. The following code is untested, but might actually work: ...
It may be overkill, but it's available from the layers & channels dialog box
Hi,
Hunter Peress <[EMAIL PROTECTED]> writes:
> Could u explain what the meta information is based on? In order to
> accomplish an undo, would this meta information be used to perform
> the inverse of an operation?
for each action the GIMP undo systems stores all of the image data
that is invali
I'll try to clarify for you.
Could u explain what the meta information is based on? In order to accomplish an
undo, would this meta information be used to perform the inverse of an
operation?
A situation where I dont think the meta information would make sense
would be: when resizing an image (u
Hi,
Hunter Peress <[EMAIL PROTECTED]> writes:
> So whats the approach for this meta information? Will u ever use this
> meta information to perform the inverse of an operation?
yes. What do you think we save it for?
> When resizing an image u lose pixels, so you would have to store size T
> in
So whats the approach for this meta information? Will u ever use this
meta information to perform the inverse of an operation?
When resizing an image u lose pixels, so you would have to store size T
in memory. No meta information there really.
On Thu, 2002-10-31 at 03:20, Sven Neumann wrote:
> Hi
Hi,
Hunter Peress <[EMAIL PROTECTED]> writes:
> Suppose 100 actions are done to an image of size T
> Would gimp's memory increase by 100T ?
it depends on what you are undoing. Only the altered tiles and the
necessary meta information to undo the action is stored in the undo
system.
Salut, Sven
Hi,
Jeff Trefftzs <[EMAIL PROTECTED]> writes:
> making sure that the layer from which you get your selection is the
> same size as the image, using (perl-fu-layer-to-image-size 1) .
> This works on the active layer only, and may not work on windows
> systems lacking perl-fu support.
oh, come on
Hi,
Martin Bernreuther <[EMAIL PROTECTED]> writes:
> I just wantet to copy a rectangle area from a source-layer to a target layer
> of an image. That's what I done first:
>
> (gimp-rect-select image 0 0 layer-width height REPLACE FALSE 0)
> (gimp-edit-copy source-layer)
> (let ((floating-sel (ca
17 matches
Mail list logo
