I did add the higherListener

I've already realised it is useless, and annoying. Just remove it. I already
have in my local version, just haven't had the time to update CVS.


Michael Bürge wrote:

> fact is: dragEvent doesn't work corectly with dynapi x when a layer is
> enabled for dragging before it has been created (which happens all the time
> in widgets)
>
> i studied the code and dicovered that this is due to the higherListener
> property not beeing set correctly, so that the mouseup/mousemove-events
> don't bubble up to the DynDocument.
> i tried to fix this, but then i came to the question if the whole
> higherListener-thing really is of any use.
> and i came to the conclusion that it is pretty useless (sorry to whoever
> added it): if the DynDocument has eventlisteners (and when using DragEvent
> thats always the case) all events have to bubble up to the DynDocument, so
> the optimization is gone (and even worse: a lot of unecessary checks for the
> higherListener property beeing set are performed).
> so my suggestion would be to remove it!
> it would only make sense if the different event-types would have their own
> higherListener-properties (higherClickListern, higherMouseDownListener,
> ...), but that would require a LOT more (complicated) code.
>
> --
> Michael Buerge
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to