I have also tried to hack/change the Layout stuff and it 
is very sensitive to any halts etc. I found that the 
newly introduced debugIt function is good 
for stuff like this. Send a self changed or some similar
message to the morph and debugIt and step until you 
get to where you want to go today :-)

Karl

PS if you get around to implement all the stuff needed to 
layout html tables with the TableLayout I'll buy you 
some beer or something similar :-)




Ross Boylan wrote:
> 
> I got out of the jam, but would still like to know why my effort to revert
> the method failed.
> 
> GridLayout removeSelector: #layout:in:
> 
> got things into a state where I could recover.
> 
> So I'm now just curious, not desperate!
> 
> At 11:36 PM 10/8/01 -0700, you wrote:
> >I would really appreciate some help so I can recover my work.  I've got
> >into a loop from a halt in the layout process, and I can't seem to undo it
> >or exit.
> >
> >History:
> >put a halt in GridLayout>>layout:in: (my own layout class)
> >this seemed to work OK, so I saved the image.
> >edited another method to force the layout
> >Tried to invoke it -> emergency evaluator.
> >
> >So:
> >reverting the last method doesn't work, because it's really the second to
> >last that's causing the trouble (I'm pretty sure).
> >Project current exit doesn't work, I suppose because the layout problem
> >interrupts it.
> >
> >Inspecting Utility>>revertLastMethodSubmission led me to try the following
> >(GridLayout changeRecordsAt: #layout:in:) second fileIn
> >but this just dumps me back into the emergency evaluator.  Further, if I go
> >(GridLayout sourceCodeAt: #layout:in:)
> >afterwards, I still see the halt.
> >
> >(Actually, I have to go (GridLayout sourceCodeAt: #layout:in:) first: 300
> >to see the relevant part of the code in the incredibly tiny emergency
> >evaluator window).