Common topic this lately, but I don't think I'm repeating anything 8-)
I've been doing some playing using the drop code and wondered about a couple of things.
1) The order in which drop events are passed to layer children
Basically, the code passes the events to the layers in the order they appear in the
children array. Surely this should also take into account the zOrder. IE if there are
multiple possible layers at the target point the "highest" layer should get tried
first and so on.
2) The drop zone size (the size of the layer being dropped onto)
As currently implemented, the drop zone must be larger in each dimension then the
layer being dropped, and the layer must be completely within the bounds of the drop
zone. This can be quite inconvenient if you are working with variably sized widgets
and multiple targets as all the potential targets must be bigger than the widgets
being dropped - a real problem if the targets are also droppable widgets! (Imagine
nestable widgets) Should it be possible to specify the size of the zone to use when
checking if the object is within the drop zone of the target?
I've implemented both of these for my own amusement[1], but I was wondering if these
were conscious design decisions, or just oversights in the implementation (both 2.53
and 20010513.)
Alistair
[1] I built an array of child IDs by zOrder, reversed this, and then used this as the
order for the checking the children; and added a magic "dragHotspot" attribute which I
check for and use in preference to the layer size for the drop tests.
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
