<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Hilaire,</p>
<div class="moz-cite-prefix">On 23/09/2025 12:42 PM, Hilaire
Fernandes via Cuis-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:79ff31dc-f38f-4283-b11d-bfc94d5cd26a@free.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font size="4">Hi Juan,<br>
</font></p>
<p><font size="4">Let me try to understand completely the
mouseMove changes. </font></p>
<p><font size="4">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?<br>
</font></p>
<p><font size="4">I am wondering if it makes the message name a
bit missleading. I was thinking it sounds more like
mouseHovering. Well, ok, maybe not.<br>
</font></p>
</blockquote>
<p><font size="4">I didn't address naming this time. We could,
though, at the cost of additional compatibility bumps. Still, a
good thing to do.</font></p>
<blockquote type="cite"
cite="mid:79ff31dc-f38f-4283-b11d-bfc94d5cd26a@free.fr">
<p><font size="4">Will not it make the UI a bit too much verbose
with this message sent systematically to each morph the mouse
is hovering?</font></p>
</blockquote>
<p><font size="4">You mean slow? The more expensive part is actually
finding the possible morph to send the event to. Once we found
it, asking it if it wants the event, or just sending it a
message that won't do anything at all is equally expensive (or
cheap).</font></p>
<p><font size="4">Thanks,</font></p>
<blockquote type="cite"
cite="mid:79ff31dc-f38f-4283-b11d-bfc94d5cd26a@free.fr">
<p><font size="4">Thanks</font></p>
<p><font size="4">Hilaire<br>
</font></p>
<div class="moz-cite-prefix">Le 23/09/2025 à 16:14, Juan Vuletich
via Cuis-dev a écrit :<br>
</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"
moz-do-not-send="true">http://mamot.fr/@drgeo</a></pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<pre class="moz-signature" cols="72">--
Juan Vuletich
<a class="moz-txt-link-abbreviated" href="http://www.cuis.st">www.cuis.st</a>
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich</pre>
</body>
</html>