maybe creating a layer = copy of the image size-way; make it invisible
(that should avoid autocropping it) and then compare it's size and
position with the cropped image.
On 8/1/07, David Feinzeig <[EMAIL PROTECTED]> wrote:
> I am writing a plugin that, among other things, autocrops an image. Bu
> On 8/1/07, David Feinzeig <[EMAIL PROTECTED]> wrote:
> > I am writing a plugin that, among other things, autocrops an image. But, I
> > need to know how much was cropped from all four sides, to deal with
> > alignment issues. Any idea how I can do this?
> >
> > Thanks!
> > Dave
If you create a
On Wednesday 08 August 2007 09:19, Owen wrote:
> 2. Do you really need to make cmyk plates?
Printing companies do, yes.
Cheers; Leon
--
http://cyberknights.com.au/ Modern tools; traditional dedication
http://www.taslug.org.au/ Member, Tasmania Linux User Group
http://slpwa.asn.au/
> On 8/1/07, David Gower wrote:
> OTOH if you're just autocropping a *layer*, not an image, you can just
> compare image corners to layer corners.
While looking into this, I notice that autocropping an image uses the
active layer, not the projection, to determine the resultant image
boundaries. (
> On 8/1/07, David Gower wrote:
> OTOH if you're just autocropping a *layer*, not an image, you can just
> compare image corners to layer corners.
While looking into this, I notice that autocropping an image uses the
active layer, not the projection, to determine the resultant image
boundaries. (
Hi,
On Wed, 2007-08-08 at 11:35 -0400,
[EMAIL PROTECTED] wrote:
> While looking into this, I notice that autocropping an image uses the
> active layer, not the projection, to determine the resultant image
> boundaries. (Would this be a bug?)
No. That's what the plug-in does and it seems that's w
[EMAIL PROTECTED] writes:
> While looking into this, I notice that autocropping an image uses the
> active layer, not the projection, to determine the resultant image
> boundaries. (Would this be a bug?)
If you want a plug-in that crops the image according to the contents
of all layers, not just t
Hi list,
I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large
(1x1pixels) photos.
This works when the tile cache is set to 256MB but this is not enough
for fast editing.
When I set the tile cache to 512MB or more it stops with error:
GLib-ERROR **: gmem.c:135: failed t
Bram Van Steenlandt wrote:
> Hi list,
>
> I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large
> (1x1pixels) photos.
> This works when the tile cache is set to 256MB but this is not enough
> for fast editing.
> When I set the tile cache to 512MB or more it stops with er
