There have been suggestions of using:
on mousedown
global amDragging
put true into amDragging
end mousedown
on mousemove
global amDragging
if amDragging then set the loc of me to the mouseloc
end mousemove
on mouseup
global amDragging
put false into amDragging
end mouseup
The problem is that Revolution misses mouseup some times, and the thing
sticks to the cursor. Even the revolution development interface suffers from
this awol-mouseup problem. Once, I tried to drag a selection box around a
group of objects, and the grey outline stuck to the cursor for a bit until I
click again. Other times, I'll click a button, and it hilights, and when I
release the mouse button it remains hilighted.
I wouldn't be forced to use mouse() if revolution actually reported mouseups
properly. Until that is fixed, I will have to continue using mouse(). I
spent almost an entire day trying to find a solution to this problem, and I
have wasted enough time on it already.
- keelan
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
