OK, following up now: I tried the test case exactly as Chris describes
below. The saved extents are working as expected.

However, I do now see one inconsistency. I have been closing the debugger
window using the red X "close this window" button to close the system
window.  In these cases, the SavedExtent works as expected - the next
debugger window uses the extent that was saved when I closed the previous
one.

But I notice now that if I proceed through the debugger so that the
debugger window closes after resuming the process, then the SavedExtent
is not updated.  I don't know if this is a bug or a feature, although I
could probably be convinced either way ;-)

Bottom line - I still cannot reproduce the problem that Chris originally
reported. The debugger window behavior seems fine to me in my working
trunk image.

Dave


On Tue, Jun 26, 2018 at 04:14:29PM -0400, David T. Lewis wrote:
> Yes, I am saying I tested it and it worked for me. I tried it several
> times using self halt it a workspace. Debuggers consistently open with the
> size as of the last one closed.
> 
> My working image is 64-bit spur that is kept up to date with trunk, and
> that has various other packages loaded.
> 
> I'll try following your recipe exactly when I get home.
> 
> Dave
> 
> > Just try to make it work once, Dave!   Are you saying you tested it
> > and it worked for you?  I just restored all preferences to default,
> > and it still fails for me.
> >
> > For goodness' sake, let me write out the most basic unit test script
> > one would use to test this..  Here:
> >
> >   step 1)   3+4   "Command+Shift+D ---  debug it"
> >   step 2)   Size the debugger to one quarter the screen size.
> >   step 3)   Close the debugger opened in step 2.
> >   step 4)   3+4   "Command+Shift+D ---  debug it"
> >   step 5)   Verify the debugger is still exactly one quarter of the screen
> > size.
> >
> > I don't see the problem with Eliots code, but I've already wasted 30X
> > more time on this than the 5 minutes originally spent to slam it into
> > trunk and neuter the years-old RealEstateAgent.  On top of that, I'm
> > feeling majorly dis'ed.  I don't care to spend any more time trying to
> > find out why abusing the Listener pattern resulted in a bug, I'll let
> > you take it from here.
> >
> > Have fun!    :/
> >
> >  - Chris
> >
> > On Tue, Jun 26, 2018 at 7:23 AM, David T. Lewis <lewis at mail.msen.com>
> > wrote:
> >> On Tue, Jun 12, 2018 at 01:17:39PM -0500, Chris Muller wrote:
> >>> Hey Eliot, this change doesn't seem to be working as designed.  I have
> >>> no idea why, but my debugger keeps opening larger and larger every
> >>> time, instead of the extent it was when it was last closed...
> >>
> >> Hi Chris,
> >>
> >> Can you say something about how to reproduce this condition? I
> >> understand
> >> that there has been follow up discussion in another thread, but I do not
> >> know how to recreate the problem.
> >>
> >> I am guessing that it is related to preference settings, but I am not
> >> sure which preferences might be involved.
> >>
> >> Thanks!
> >>
> >> Dave
> >>
> >>
> >>>
> >>> On Sun, Jun 3, 2018 at 1:30 PM <commits at source.squeak.org> wrote:
> >>> >
> >>> > Eliot Miranda uploaded a new version of Tools to project The Trunk:
> >>> > http://source.squeak.org/trunk/Tools-eem.817.mcz
> >>> >
> >>> > ==================== Summary ====================
> >>> >
> >>> > Name: Tools-eem.817
> >>> > Author: eem
> >>> > Time: 3 June 2018, 11:30:18.12214 am
> >>> > UUID: e29d1a74-c6b6-4752-b4d0-b735061f4c9f
> >>> > Ancestors: Tools-mt.816
> >>> >
> >>> > In the absence of proper support from RealEstateAgent and the tool
> >>> builder, provide a memory of the debugger's last extent, and use it
> >>> when opening a full debugger.
> >>> >
> >>> > =============== Diff against Tools-mt.816 ===============
> >
> >
> 
> 
>