At 2:32 PM -0700 10/5/01, Bill Vlahos wrote:
>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):
Ack! Turns out mouseEnter and mouseExit are only sent to the topmost object. Dragging
the mouse down through:
---------------------------------
|
Button 1 |
|
--------------------- |
| |
Button 2 | |
| |
| |
--------------------- |
|
|
---------------------------------
Would result in a mouseEnter to Button 1,
then a mouseExit to Button 1 and a mouseEnter to button 2,
then a mouseExit to button 2 and a mouseEnter to button 1,
then a mouseExit to button 1.
In other words, as you drag an object around, nothing gets a mouseEnter or exit
because the pointer is always inside the object you're dragging.
All of which is a long-winded way of saying I don't have a good answer. :-)
regards,
Geoff
