[Cuis-dev] Recent changes in MouseEvent dispatching and Kayboard focus and events

[Hilaire Fernandes]

Hi Juan,

Let me try to understand completely the mouseMove changes.

So you don't need anymore handlesMouseDown: answering true to get the 
message #mouseMove.. sent to each morph the mouse is hovering, is that 
correct?

I am wondering if it makes the message name a bit missleading. I was 
thinking it sounds more like mouseHovering. Well, ok, maybe not.

Will not it make the UI a bit too much verbose with this message sent 
systematically to each morph the mouse is hovering?

Thanks

Hilaire

Le 23/09/2025 à 16:14, Juan Vuletich via Cuis-dev a écrit :
> - MouseMoveEvent. Before, only morphs that answered true to 
> #handlesMouseDown: would get them. Except for InnerTextMorph that used 
> them to highlight and enable links in text. This made me think that 
> any morph could make good use of MouseMove event if no mouse button is 
> pressed. So I made that change. Now, most implementors of 
> #mouseMove:localPosition: need to ask `aMouseMoveEvent 
> anyButtonPressed` before doing their stuff. Your morphs should most 
> likely do the same. 

-- 
http://mamot.fr/@drgeo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20250923/e1b293fc/attachment.htm>