VB Suggestion
4 messages in this thread
Don,
Using DragDrop, as shown in the example in online help, gives a problem.
If the user "drops" the outline while he's over a control, and that
control's DragOver event has set the MousePointer of the Source to 12, then
the Source Mousepointer remains at 12. Right now, the only workaround is to
code a DragDrop routine in each of the controls that has a DragOver so that
Source.Mousepointer is set back to zero.
So, my suggestion is that when the user does a drag-drop, either he should
get a Source_MouseUp event, or a new event to indicate dragging has
finished.
Mark
Mark,
I told them about this problem waaay back in May. I ran into that problem
in my prototype charting application. After talking to John Fine and Adam
Rauch, apparently it's not so easy to get a MouseUp event sent out, but I'm
holding out for 2.0 to have this feature. I'm glad I'm not the only one
who found this to be a problem!
– Ted
There is 1 Reply.
Ted,
I can accept no MouseUp event if they'd just give us a *new* event –
DragDone – anything to avoid all that code in all the DragDrop routines…
Mark
There is 1 Reply.
Mark,
I'd accept anything that told me the dragging was done and a DragDone would
be nice event. I still think that if I get a MouseDown and start dragging
programatically (doing Drag.1), I should get a MouseUp. However, a
DragDone event would be more generic and would be very useful also.
Hey Don, did you get this for the must-have-in-2.0 list?
– Ted