<div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000"><div>Hi Stef,</div><div><br></div><div>First, let me acknowledge that this is kind of a regression. :-)</div><div><br></div><div>Now, what is the situation here:</div><div><br></div>
1) Morphs used to be in control by overwriting #handleMouseDown: to avoid the invocation of the meta menu. I changed this by moving the code to PasteUpMorph >> #tryInvokeMetaMenu:. <b>My intention is still to increase the robustness of the system in the face of erroneous morphs.</b><div class="mb_sig"></div>
<div><br></div><div>2) The check for #wantsMetaMenu is not sufficient in this case because you have to control the entire ownership of a morph to avoid the meta menu. At least the (Morphic) world will give you its meta menu.</div><div><br></div><div>3) It would be nice to only invoke the meta menu for CTRL+YELLOW so that CTRL+RED could be used for something different. This is not possible due to automatic conversions in the VM. So, at the moment the code fires on CTRL+ANYTHING. <b>This is bad because it wastes user-input gestures as you discovered in your code.</b></div><div><br></div><div>4) The preference "cmdGesturesEnabled" is rather misleading. It looks like we need a "morphicMetaMenuEnabled" preference, which works system wide but can be disabled for muO or other applications.</div><div><br></div><div>5) If we, as you proposed, would add code that allows individual morphs to bypass this generic development tool (i.e. the meta menu), <b>we would decrease the robustness of the system again.</b> That's why I disagree with your change.</div><div><br></div><div>***</div><div><br></div><div>The bottom line is that you should disable the command gestures via "Preferences disable: #cmdGesturesEnabled". I think we should split up this preference into "morphicHaloEnabled" and "morphicMetaMenuEnabled". By disabling #<span style="font-size: 12pt;line-height: 1.5">cmdGesturesEnabled,</span><span style="font-size: 12pt;line-height: 1.5"> your morphs need to open their halo manually such as via #mouseDown: calling #invokeHaloOrMove:. :-)</span></div><div><br></div><div>If you have more questions, keep on asking. The meta menu is a dev tool, which must work under any circumstances.</div><div><br></div><div>Further readings:</div><div><a href="http://forum.world.st/Please-Review-Map-CTRL-red-to-CTRL-yellow-and-CMD-red-to-CMD-blue-td4913716.html">http://forum.world.st/Please-Review-Map-CTRL-red-to-CTRL-yellow-and-CMD-red-to-CMD-blue-td4913716.html</a></div><div><a href="http://forum.world.st/How-to-yellow-click-with-two-buttons-without-changing-mouse-settings-tp5074670p5074775.html">http://forum.world.st/How-to-yellow-click-with-two-buttons-without-changing-mouse-settings-tp5074670p5074775.html</a></div><div><a href="http://forum.world.st/How-to-yellow-click-with-two-buttons-without-changing-mouse-settings-tp5074670p5075027.html">http://forum.world.st/How-to-yellow-click-with-two-buttons-without-changing-mouse-settings-tp5074670p5075027.html</a></div><div><br></div><div>Sorry for any inconveniences...</div><div><br></div><div>Best,</div><div>Marcel</div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 11.05.2018 12:17:36 schrieb Stéphane Rollandin <lecteur@zogotounga.net>:</p> > The actual issue is still RED -> YELLOW. That's why the meta menu is<br> > invoked in the first place. Your suggestion/fix is a rather unstable<br> > workaround. :-/ Sure, you can make it work for a single application.<br> > Yet, it breaks in the general sense.<br><br><br>I do not understand what you mean by unstable. What is wrong with <br>testing that the CTRL key is pressed during a mouseMove:?<br><br>I do not understand either what you mean by "work for a single <br>application". My code lets each Morph subclass decides if it wants the <br>meta menu or not. It doesn't change anything to the behavior of morphs <br>that do not explicitely reject it. So what is it breaking?<br><br>I have had this working for years in muO. The reason I am proposing some <br>code now is that I just realized, in the process or porting muO to <br>Squeak 6, that it has become much simpler to implement now, thanks to <br>your refactoring BTW.<br><br>Please have a look at the image I just uploaded at<br>http://zogotounga.net/swap/CtrlDrag.zip and see by yourself if there is <br>anything unstable there.<br><br>Again, what I propose is just and only to be able to escape the meta <br>menu mechanism. What is the justification for not allowing a way to bail <br>out of it?<br><br><br>Best,<br><br>Stef<br><br>
</blockquote></div>