problematic scenes

Sven Langkamp sven.langkamp at gmail.com
Mon Aug 24 21:59:02 CEST 2009


On Mon, Aug 24, 2009 at 9:06 PM, Vera Lukman <vla24 at sfu.ca> wrote:

>
> pic1 http://i230.photobucket.com/albums/ee276/shicmap/1.png
> pic2 http://i230.photobucket.com/albums/ee276/shicmap/2.png
> pic3 http://i230.photobucket.com/albums/ee276/shicmap/3.png
>
> This is a problem that I am having right now.
>
> pic1 is what pic3 is supposed to look like.
> To produce the problem:
> 1. open the drop down box for paintop
> 2. click save to palette button to see palette manager
> 3. open the drop down box again.
>
> The problem is because I "borrow" the settings widget from paintopBox. When
> the settings widget is passed to be used for layout in PaletteManager, the
> object gets deleted! I wonder if there is a way to clone the settings widget
> so a clone will be passed to the layout.
>

This is the same bug as here: https://bugs.kde.org/show_bug.cgi?id=174356
At the moment each paintop can only have one settings widget and once that
get deleted you don't get it back. I had the same problem when I implemented
the saving of presets (I wonder if this might be doing the same).

The way to solve this is to allow the the paintop factory to create settings
widgets and decouple the paintop settings from the widget. So instead of
having a pointer to the widget in the settings object you would write the
settings into it. I tried to do that, but I haven't finished that yet. At
the moment I'm a bit stuck with KisPaintOpOption data that needs to be saved
and read from the settings object.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20090824/d88659bc/attachment.htm 


More information about the kimageshop mailing list