On Jul 12, 2006, at 8:25 AM, Karen wrote:
We built a new version of our app (with r3) on Friday and released
it to our end users - we are getting feedback that listbox drag
and dropping is not working as it did before, with r2 built apps.
The situation:
Two listboxes, with the ability to drag from lb1 to lb2. We
provide some visual feedback in lb2 where the dragged row is going
- that is all working fine. Except that now lb2 will not accept
the drop.
The reason? The lb2 DragExit event is firing *before* the lb2
DropObject event, and blowing out some of our properties.
Has the DragExit event always fired on a *target* listbox before
the DropObject event when dropping?
I was working on a project in R2 where i was dragging individual
cells from one listbox to another, I had that part working fine and
i don't recall seeing that behavior...
I had to put that project to the side for awhile because of time
constraints but hope to get back to it soon with R3... hopefully
that will still work! ... If not, back to R2.
PS...
I think if DropObject fires DragExit SHOULD not because the object
being dragged never exits... after all it was dropped there!
My understanding was that DragExist in the companion to DragEnter to
track movement into and out of a given control, not to mark the end
of the drag if dropped...
And DragEnter/DragExit should not fire unless the control can accept
that drop...
I vaguely recall seeing inconstancies Xplatform in these behavior but
I may be wrong.
- Karen
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
