Geoff, Thanks for the suggestion but it didn't work. Any other suggestions?
Bill Vlahos On Thursday, October 4, 2001, at 06:00 PM, use-revolution- [EMAIL PROTECTED] wrote: > At 6:17 PM -0700 10/3/01, Bill Vlahos wrote: >> What I want to do now is move an object (like a button) onto any one of >> a number of objects. Before I let go of the object I'm moving, have the >> other object hilite to give feedback that it is over something >> useful. I >> can get the target object to hilite using mouseEnter or mouseWithin >> if I >> simply move the mouse over it but those messages don't get to the >> target >> if I am dragging the button. There will be too many target objects for >> me to check overlap with all of them. > > > At 2:04 PM -0700 10/1/01, Geoff Canyon wrote: >> If you need to do other things while the drag is happening (grab >> blocks other code from executing) then try the mouseMove message >> instead of mouseStillDown. > > Specifically, something (untested) like this should allow the delivery > of mouseEnter and mouseExit messages (avoid mouseWithin -- mmessages > are relatively costly so instead set a variable on entry and exit. to > avoid making the engine work harder than it has to): > > local draggingMe > > on mouseDown > put true into draggingMe > end mouseDown > > on mouseUp > put false into draggingMe > end mouseUp > > on mouseMove x,y > if draggingMe then > set the loc of me to x,y > end if > end mouseMove > > regards, > > Geoff
