> > 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
I'm guessing here, but I think you'll find the problem is that the Revolution interface also uses "mouse()" and mouseloc within a repeat loop! Yes, they seem to be learning too! So until they fix their bit it's unlikely your stack will run well unless it's outside of the development environment. I wrote a time clock, a scale that represents the 24 hours, and then little flags you can drag on to the scale to indicate you want to do something at that given time. With so much dragging around it worked poorly until I changed the code to do the method you mentioned (i.e. The so called proper way). Within Revolution the little flags still stuck to my mouse, hence they seemed to miss a mouseup or mouserelease. BTW: don't forget to trap the mouserelease too, I'm not so sure you'll always get a mouseup, if you manage to release the mouse while the mouse is outside your control then it'll send mouserelease (I guess if your dragging fast this could happen!) Anyway, my stuff is working fine now, I put it down to the Revolution interface doing naughty things. Have a nosey through their scripts, you'll see what I mean. _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
