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

List:       kde-kimageshop
Subject:    Re: koffice/krita
From:       "Casper Boemann" <cbr () boemann ! dk>
Date:       2005-04-28 11:50:04
Message-ID: 046601c54be8$6b3357f0$1c90a8c0 () FKIBM13045
[Download RAW message or body]

Thanks. I'll stick to you solution. Then later we can reexamine what can be
done.

best regards / venlig hilsen
Casper Boemann
----- Original Message ----- 
From: "Sven Langkamp" <longamp@reallygood.de>
To: "Krayon (KImageShop)" <kimageshop@kde.org>
Sent: Thursday, April 28, 2005 1:29 PM
Subject: Re: koffice/krita


> Am Donnerstag, 28. April 2005 09:22 schrieb Casper Boemann:
> > Hi
> >
> > Thanks. This ties in with what I'm looking at. (I even got a merge
> > conflict - that's how close it ties)
> >
> > I was wondering what kind of observations you made to come to this
> > solution.
> I followed the signals and slots. The whole connection was
KisPaintDevice ->
> KisImage -> KisView -> KisDockManager. Then I looked for the gap: KisImage
> connected itself with signal from the paintdevice without a connection
error,
> but the signal did never reach the slot.
>
> > Did the signal not work at all?
> > Wont it be a limit to change a signal (which is many-to-many) into a
> > function (which is many-to-one)? Or am I missunderstanding your change?
> I guess that you can't connect to a signal from a shared pointer( in this
case
> layer.data() ) As I wrote wrote earlier to the list, I'm not really happy
> with that and I'm open for a better solution.
> Instead of directly connecting to the paintdevice you can connect to the
> KisImage.
> _______________________________________________
> kimageshop mailing list
> kimageshop@kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
>


_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]