Apparently the process dies somewhere inside openWithTitle:; maybe someone knows off the top of his head, where, what's the matter, and what's the right way of doing in this situation?
If you follow the chain of messages down from openWithTitle:, you find yourself at
ControlManager>>scheduleActive:
which says:
scheduleActive: aController "Make aController be scheduled as the active controller. Presumably the active scheduling process asked to schedule this controller and that a new process associated this controller takes control. So this is the last act of the active scheduling process." <primitive: 19> "Simulation guard" self scheduleActiveNoTerminate: aController. Processor terminateActive
So the last act of openWithTitle: is to terminate the current process. This is the standard problem with opening a new controller -- it must be the last thing that you do.
If you want to continue to execute code after the open, you will have to use the ControlManager>>scheduleActiveNoTerminate: message, but that would involve duplicating a lot of the messages in the path of control from openWithTitle:
-- tim
squeak-dev@lists.squeakfoundation.org