I've just started trying to make more use of the code pane in Spotter.  It
seemed ideal for the case when I want to add "self haltOnce" to a dozen
methods.  However when I hit <enter> to get a new line, Spotter closes.

Additionally the Browser that opens doesn't contain the change I made in
Spotter - they've been thrown away.

 I propose that when the cursor is inside the code pane, it doesn't close
Spotter.   Even at this late stage, could this be done for Pharo 4?  Only
because I am guessing this since Spotter is a core tool, this might end up
a common complaint as people adapt their workflow to use Spotter more.

Would it be safer at this late stage prior to Release that this be done as
a Slice, to limit other changes that might come through the Spotter
Configuration?

cheers -ben

Reply via email to