<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>> <span style="font-size:12pt">*An exception could be if the selected selector is the selector of the </span><span style="font-size:12pt">current method. Then it could make sense to add to the trace instead. </span><span style="font-size:12pt">But I would
not insist on that special case.</span></p>
<div><br>
</div>
<div>-1 for the extra complexity in the UI. :-)</div>
<div><br>
</div>
<div>> <span style="font-size:12pt">That the buttons behave differently than the menu items in the code </span><span style="font-size:12pt">editor is actually inconsistent, but knowing that, I have become </span><span style="font-size:12pt">accustomed to using
them if I do want a new window. I would not be too</span>
<div>concerned if that would change though (then they should behave like <span style="font-size:12pt">the actions in the code editor).</span></div>
<div><br>
</div>
<div>I have accustomed too, and I think we should always provide this "last resort" for opening a new window. It's pretty straightforward for me: Use your mouse if you want a new window, or use the keyboard if you want to stay in the existing window. On the
other hand, in this model, we would probably also need to revise the behavior of the menu items. :-)</div>
<div><br>
</div>
<div>Best,</div>
<div>Christoph</div>
</div>
<p></p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Jakob Reschke <jakres+squeak@gmail.com><br>
<b>Gesendet:</b> Freitag, 14. Januar 2022 20:09:44<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] bad MessageTrace regression (was: The Trunk: Morphic-mt.1652.mcz)</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Marcel,<br>
<br>
Am Fr., 14. Jan. 2022 um 17:05 Uhr schrieb Marcel Taeumel<br>
<marcel.taeumel@hpi.de>:<br>
><br>
> Aha! So, my misinterpretation was to read "browse senders" but understand "browse senders/implementors".<br>
><br>
<br>
That was also my impression when I read your emails while cooking<br>
lunch today. ;-)<br>
<br>
FWIW here are my expectations:<br>
- Menu and keyboard shortcut do the same thing<br>
- Senders in the message list: add to trace<br>
- Implementors in the message list: add to trace (but is seldom<br>
useful, only if you have previously deleted too many items from the<br>
trace)<br>
- Senders in the code editor: new window*<br>
- Implementors in the code editor: add to trace<br>
- Senders/Implementors Buttons: new window<br>
<br>
*An exception could be if the selected selector is the selector of the<br>
current method. Then it could make sense to add to the trace instead.<br>
But I would not insist on that special case.<br>
<br>
That the buttons behave differently than the menu items in the code<br>
editor is actually inconsistent, but knowing that, I have become<br>
accustomed to using them if I do want a new window. I would not be too<br>
concerned if that would change though (then they should behave like<br>
the actions in the code editor).<br>
<br>
Kind regards,<br>
Jakob<br>
<br>
</div>
</span></font>
</body>
</html>