[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    Fwd: Re: [Kde-imaging] Manipulating image data from within a KIPI
From:       blackie () blackie ! dk (Jesper K !  Pedersen)
Date:       2004-05-23 15:38:53
Message-ID: 200405231538.20152.blackie () blackie ! dk
[Download RAW message or body]

On Friday 21 May 2004 23:49, Aurelien Gateau wrote:
| 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.
OK, so what we really need is a new KIPI::Category for this so that we could 
place these plugins with the viewer.

May I suggest that the image() method is located in KIPI::ImageInfo then.

Cheers
Jesper
[prev in list] [next in list] [prev in thread] [next in thread]