<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> 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 <div class="moz-cite-prefix">Le 23/09/2025 à 16:14, Juan Vuletich via Cuis-dev a écrit : </div> <blockquote type="cite" cite="mid:ca7c754e-ca53-4a74-b85d-6412b226d3d8@cuis.st">- 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 #<a class="moz-txt-link-freetext" href="mouseMove:localPosition" moz-do-not-send="true">mouseMove:localPosition</a>: need to ask `aMouseMoveEvent anyButtonPressed` before doing their stuff. Your morphs should most likely do the same. </blockquote> <pre class="moz-signature" cols="72">-- <a class="moz-txt-link-freetext" href="http://mamot.fr/@drgeo">http://mamot.fr/@drgeo</a></pre> </body> </html>