<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Chris,<div><br></div><div>that's the correct fix. :-)</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 25.04.2019 20:59:15 schrieb Chris Muller <asqueaker@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">> > I just tried those steps. I can reproduce the problem when I click in
<br>> > the *gray area* (e.g., parent-most morph) on the right side of the
<br>> > halos, but when its in that same gray area on the left hand side, or
<br>> > any other morph like the Help button, it works. Very strange. There
<br>> > must be something unique about this particular "Same" game's Morph
<br>> > structure or w.r.t. how it interacts with the new implementation of
<br>> > #tryInvokeHalo:. This is the first Morph I've seen behave this way.
<br>>
<br>> No, the bug is very general - I just gave fast and easy steps to
<br>> reproduce it. But you can just compose three morphs (Morph instances), a
<br>> big one with two smaller ones as children, and you get the same problem
<br>> in areas where the top morph overlaps a system window.
<br>
<br>Strange, I just wrote the following code to try it:
<br>
<br>| a b c| a := Morph new extent: 200@200.
<br>b := Morph new color: Color green; position: 50@50.
<br>c := Morph new color: Color yellow; position: 100@100.
<br>a addMorphBack: b; addMorphBack: c; openInHand
<br>
<br>and it worked. But then, I did it again, and it didn't.
<br>
<br>> As I said, the problem is "simply" that #tryInvokeHalo: builds a stack
<br>> of potential targets at the clicked point, then for some reason that I
<br>> did not investigate discards the first one with the explicit comment
<br>> "existingHalo is first on the stack, not a target", while it *is* the
<br>> target here.
<br>
<br>Ah! That's the clue we needed. I'm not exactly sure why the halo
<br>morph wouldn't be the top one on the stack either, but this patch uses
<br>a much more-resilient way to do that. Let me know if this works,
<br>we'll commit it to trunk.
<br>
<br>Best,
<br> Chris
<br><br></div></blockquote>
</div></body>