<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Hi Chris,</p>
<p><br>
</p>
<p>nice issue! I agree this would be an improvement in debugging scenarios.</p>
<p><br>
</p>
<p>However, when I press Shift + ArrowRight to extend the selection, I would indeed expect that the cursor is scrolled into view. I think we would need to distinguish between "machinal selection" and "selection by user."</p>
<p>And shouldn't we respect the selection orientation here (i.e., which of markIndex and pointIndex is larger - see TextEditor >> #exchange)?</p>
<div id="Signature">
<div id="divtagdefaultwrapper" dir="ltr" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica, sans-serif, EmojiFont, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols;">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div class="_rp_T4" id="Item.MessagePartBody"><br>
</div>
<div class="_rp_T4" id="Item.MessagePartBody">But I would rather dislike a preference, imho we should make it dependent on the origin of the selection (machine vs. user) to achieve the best convenience.
<div class="_rp_U4 ms-font-weight-regular ms-font-color-neutralDark rpHighlightAllClass rpHighlightBodyClass" id="Item.MessageUniqueBody" style="font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont">
<div dir="ltr">
<div id="divtagdefaultwrapper"><font face="Calibri,Helvetica,sans-serif,EmojiFont,Apple Color Emoji,Segoe UI Emoji,NotoColorEmoji,Segoe UI Symbol,Android Emoji,EmojiSymbols">
<div id="Signature">
<div style="margin:0px"><font style="font-family:Calibri,Arial,Helvetica,sans-serif,serif,EmojiFont"></font></div>
</div>
</font></div>
</div>
</div>
</div>
<div class="_rp_T4" id="Item.MessagePartBody"><br>
</div>
<div class="_rp_T4" id="Item.MessagePartBody">Best,</div>
<div class="_rp_T4" id="Item.MessagePartBody">Christoph</div>
</div>
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Chris Muller <asqueaker@gmail.com><br>
<b>Gesendet:</b> Donnerstag, 2. Januar 2020 03:30:48<br>
<b>An:</b> squeak dev<br>
<b>Betreff:</b> [squeak-dev] stepping in small panes</font>
<div> </div>
</div>
<div>
<div dir="ltr">Hi all,
<div><br>
</div>
<div>When debugging on a small screen and a larger font, block expressions can easily overrun the size of the text pane. Currently when stepping, selecting a stack frame, clicking Where -- anything that changes the text selection, it positions you to the bottom.</div>
<div><br>
</div>
<div></div>
<div>
<div><img alt="show-bottom-sel.png" width="519" height="493" src="cid:ii_k4w3qbiv0"><br>
</div>
<div><br>
</div>
<div>Unfortunately, this makes debugging cumbersome, because I need to see the beginning of the selection instead of the end, to know what I'm stepping through.<br>
</div>
<div><br>
</div>
<div>
<div><img alt="show-top-sel.png" width="519" height="493" src="cid:ii_k4w3xmic1"><br>
</div>
</div>
<div><br>
</div>
<div>I use soft wrap, so don't face any issue along the horizontal dimension, but for the same principle, Morphic-cmm.1614 treats it similarly.</div>
<div><br>
</div>
<div>Before:</div>
<div>
<div><img alt="show-right-sel.png" width="222" height="528" src="cid:ii_k4w41nue2"> VS <br>
</div>
<div><img alt="show-left-sel.png" width="222" height="528" src="cid:ii_k4w42cx63"><br>
</div>
</div>
<div><br>
</div>
<div>What do you think? Preference-worthy?</div>
</div>
<div><br>
</div>
<div>Best,</div>
<div> Chris</div>
</div>
</div>
</body>
</html>