<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Christoph,<div><br></div><div>it has "always" been that way.. I suppose that its (a) for performance reasonse and (b) you are "stopping time" when debugging anyway. :-)</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 01.10.2020 13:56:55 schrieb Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de>:</p><div style='font-family:Arial,Helvetica,sans-serif'>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size: 12pt;color: #000000;font-family: Calibri,Helvetica,sans-serif">
<p>Hi Marcel,</p>
<p><br>
</p>
<p>just a basic question - why do we disable stepping in Debuggers? :-)</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
<div id="x_Signature">
<div id="x_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="x_divtagdefaultwrapper" style="font-family: Calibri,Arial,Helvetica,sans-serif;font-size: ;margin: 0">
<div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">
<div class="x__rp_U4 x_ms-font-weight-regular x_ms-font-color-neutralDark x_rpHighlightAllClass x_rpHighlightBodyClass" id="x_Item.MessageUniqueBody" style="font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif,serif,EmojiFont">
<div dir="ltr">
<div id="x_divtagdefaultwrapper"><span style="font-family: Calibri,Helvetica,sans-serif,EmojiFont,Apple Color Emoji,Segoe UI Emoji,NotoColorEmoji,Segoe UI Symbol,Android Emoji,EmojiSymbols">
<div id="x_Signature">
<div style="margin:0px"><font style="font-family:Calibri,Arial,Helvetica,sans-serif,serif,EmojiFont">
<div><font size="3" color="black"><span style="font-size: 12pt"><a href="http://www.hpi.de/" target="_blank" rel="noopener noreferrer" id="LPNoLP"><font size="2"><span id="LPlnk909538"><font color="#757B80"></font></span></font></a></span></font></div>
</font></div>
</div>
</span></div>
</div>
</div>
</div>
</div>
<div><span style="font-size: 10pt;color: #808080"></span></div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif;color: #000000"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von commits@source.squeak.org <commits@source.squeak.org><br>
<b>Gesendet:</b> Dienstag, 29. September 2020 10:20:36<br>
<b>An:</b> squeak-dev@lists.squeakfoundation.org; packages@lists.squeakfoundation.org<br>
<b>Betreff:</b> [squeak-dev] The Trunk: Tools-mt.990.mcz</span>
<div> </div>
</div>
</div>
<span style="font-size: 10pt"><span style="font-size: 10pt">
<div class="PlainText">Marcel Taeumel uploaded a new version of Tools to project The Trunk:<br>
<a href="http://source.squeak.org/trunk/Tools-mt.990.mcz">http://source.squeak.org/trunk/Tools-mt.990.mcz</a><br>
<br>
==================== Summary ====================<br>
<br>
Name: Tools-mt.990<br>
Author: mt<br>
Time: 29 September 2020, 10:20:33.276444 am<br>
UUID: e7da396b-a8ec-7a44-8f15-5ba7d0d30b37<br>
Ancestors: Tools-mt.989<br>
<br>
In debuggers, forward model-wake-up call to update inspectors. This fixes the bug where a 'nil' receiver had no fields in the receiver inspector. For example, try debug-it on any expression in the workspace to trigger that bug.<br>
<br>
Note that the underlying challenge is that the inspectors in debuggers are not stepping. Field updates are triggered manually via #updateInspectors. An inspector's initial object is 'nil'. So, "changing" that to 'nil' will not update the field list in inspectors
bc. it is considered redundant and will be ignored there. While stepping is not required to produce the initial field list, the model-wake-up call will usually trigger that initial update in a stand-alone inspector.<br>
<br>
That's why I think that it is not necessary to change anything in the inspector code but only here in the debugger.<br>
<br>
=============== Diff against Tools-mt.989 ===============<br>
<br>
Item was added:<br>
+ ----- Method: Debugger>>modelWakeUpIn: (in category 'user interface') -----<br>
+ modelWakeUpIn: aWindow<br>
+ <br>
+ super modelWakeUpIn: aWindow.<br>
+ self updateInspectors.!<br>
<br>
<br>
</div>
</span></span>
</div></blockquote>
</div></body>