Re: Gimp-python: Artefacts when creating layer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday 03 June 2006 09:53 am, Simon Budig wrote:
> Alan Horkan (horkana@xxxxxxxxxxxx) wrote:
> > On Sat, 3 Jun 2006, Simon Budig wrote:
> > > That sounds as if you don't clear the layer before you use it
> > > for the first time. Layers created from a Plugin are not
> > > initialized from the very beginning. They need to be cleared
> > > using e.g. gimp_drawable_fill.
> >
> > I remember getting caught out by this too.  Why is necessary to
> > manually clear a new layer rather than have it done
> > automatically?
>
> I have no strong opinions on that. I guess the reasoning behind
> this behaviour was a speed optimization: If a plugin later renders
> stuff to a new layer anyway it would be a waste of time to clear it
> automatically. If it doesn't it would just invoke
> gimp_drawable_fill. No harm done, except that you have to know
> about it.
>
> It might even matter for big images...
>


For C plug-ins  that might be true. However, python plug-ins are not 
good in dealing directly with pixels - that is, for rendering things.

I guess the python api for creating a layer could create an empty one 
with no problems.

Regards,
	JS
	-><-

> Bye,
>          Simon
_______________________________________________
Gimp-developer mailing list
Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux