unexpected messages

[J. Landman Gay]

On 4/22/03 10:29 PM, Bob Rasmussen wrote:

> But, as I noted, the mouse had *not* moved.  The mouseMove message was triggered by a "hide"
> command in a mouseDown handler, *not* by any mouse movement.  Why?  And what other surprises are
> in store?

I bet it has something to do with changes in the new engine.  A 
mouseEnter/mouseLeave message is now sent when moving a control or 
changing a control's visibility if the control is located at the current 
mouseLoc. I wonder if an extra mousemove gets sent as well.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com