Fwd: Re: [Kde-imaging] Manipulating image data from within a KIPI plugin

[Aurelien Gateau]

Le jeudi 20 Mai 2004 23:44, vous avez écrit :
> On Thursday 20 May 2004 23:37, Aurelien Gateau wrote:
> | > OK, I think I'm almost there now ;-)
> | > I could as easy as scratching my back return a QImage from say KimDaBa,
> | > but where should this image be displayed? Would a call to this QImage
> | > method indicate to the host application that it should display the
> | > image in a viewer?
> |
> | No, image() returns a reference to the image data loaded by the host app.
> | The plugin uses this reference to modify the image (the reference is not
> | const). Once the plugin has modified the image, it will notify the host
> | app by calling setImageDirty(). The host app implementation of
> | setImageDirty() should refresh the image view and consider it as
> | modified, so that it can warn the user of unsaved changes if he quits.
>
> I do understand that the image is not const, but you still haven't told me
> what makes that image appear on my monitor in the first place.

The QImage returned by image() is the current image in the viewer. In KimDaBa 
for example, you can double click on a image to open a window showing the 
image in full size. You could start KIPI plugins from within this window to 
manipulate the image.