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

List:       koffice-devel
Subject:    Re: dependee
From:       Jan Hambrecht <jaham () gmx ! net>
Date:       2007-12-18 9:46:25
Message-ID: 476796F1.6020206 () gmx ! net
[Download RAW message or body]

Thomas Zander wrote:
> On Monday 17 December 2007 23:57:11 jaham wrote:
>>> 3) any shape that is at a similar position as another shape there is
>>> collision detection. You can register your shape to be sensitive to any
>>> changes like moving or whatever to *other* shapes that intersect yours.
>>> Such changes will then be notified to your shape using the method from
>>> (1) You should call KoShape::setCollisionDetection(bool) to enable
>>> this.
>> There is no guarantee that dependent shape do interse
> 
> I don't follow this; both your usecases have shapes that intersect.
> Which usecase were you thinking about where intersection is not applicable 

Cloned shapes do not intersect. And even connections do not necessarily 
intersect, depending on where the glue points are.
And from what i can see in the collision detection code at the shape 
manager, it is dependent on the z-index of the shapes colliding which 
would make it a fragile thing imho to use for these cases.


> AND your backend doesn't know about shapes (like different text shapes 
> group together to make one story) ?

And can you please explain what you mean with backend in that context?

> 
> Or, in other words; what existing functionality would you loose if you 
> ported your usecases to the pre existing notification methods and avoided 
> using the dependee feature?
> 

See above.

Ciao Jan

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