On Mon, Nov 11, 2019 at 1:40 AM Ofnuts wrote:
> On 11/10/19 5:23 AM, Dan Hitt via gimp-developer-list wrote:
> > The other hole is that i find that so far i cannot read and write a
> > pixel.
>
>
> From my experiments:
>
> - start an "undo group": this marks the image "dirty"
>
> - attach an
On 11/10/19 5:23 AM, Dan Hitt via gimp-developer-list wrote:
The other hole is that i find that so far i cannot read and write a
pixel.
From my experiments:
- start an "undo group": this marks the image "dirty"
- attach an "undoable" parasite
- end the undo group and exit
At that point if
On Sat, 2019-11-09 at 20:23 -0800, Dan Hitt wrote:
> . So to properly do this simple operation of reading and
> writing
> a pixel, one should go through the gegl interface.
You could look at the source for existing plugins, especially in
2.10.14, for examples.
> (And glad you get to mess
On Fri, Nov 8, 2019 at 7:53 PM Liam R E Quin wrote:
> On Fri, 2019-11-08 at 18:40 -0800, Dan Hitt via gimp-developer-list
> wrote:
> > But i don't
> > see
> > how you can mark an image as dirty.
>
> Write some data to the image?
>
> E.g. read a pixel and write it back again?
>
> > I'm using
On Fri, 2019-11-08 at 18:40 -0800, Dan Hitt via gimp-developer-list
wrote:
> But i don't
> see
> how you can mark an image as dirty.
Write some data to the image?
E.g. read a pixel and write it back again?
> I'm using gimp 2.10.8 on debian 10.
You might want to update to 2.10.14. the current
I'm writing a plugin that adds some metadata to an image (gimp document).
The metadata is added as a "parasite".
I can see in the api, libgimp/gimpimage_pdb.h, how you can test if an image
is dirty, via gimp_image_is_dirty(image_id). I can also see how you can
mark an image as clean
