I've spent some time in the past in that part of the debugger but still can't say which approach is better.

Anyway, in the new debugger you can say: �
� � � aDebugger code pendingText: 'something'


Cheers,
Andrei


On Wed, Apr 10, 2013 at 9:24 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Igor, couldn't agree more. Plus there are problems with both my approaches...


Sean P. DeNigris wrote
> aDebugger getTextMorph textMorph editor selectAll.
> aDebugger getTextMorph textMorph editor zapSelectionWith: aString.

"Works if wrapped in "sourcePane handleEdit: []", but warns that the method
has been edited elsewhere. Without the wrapping, it looks like it has
accepted, but keeps the old source (i.e. when I browse the method, the
source was not accepted).


Sean P. DeNigris wrote
> aDebugger getTextMorph textMorph contents: 'meaning: aString
> � � � meaning := aString.'
> aDebugger getTextMorph textMorph editor userHasEdited

Warns that the method has been edited elsewhere; if you click okay, it looks
like it has accepted, but keeps the old source (i.e. when I browse the
method, the source was not accepted).



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669p4680679.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.