stephane ducasse wrote
> Then sean did you look at the new debugger model?
I want to use this in 2.0, so it seems I'm stuck with the old debugger for
now.
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Replacing-all-text-in-a-code-pane-tp4680669p4680734.html
Sent fro
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 wrote:
> Igor, couldn't agree mor
Alain is rewriting textMorph so it will get better.
Then sean did you look at the new debugger model?
Stef
On Apr 10, 2013, at 8:38 PM, Igor Stasenko wrote:
> On 10 April 2013 20:08, Sean P. DeNigris wrote:
>> I'm writing a little debugger extension and I want to replace the entire
>> method s
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 meth
On 10 April 2013 20:08, Sean P. DeNigris wrote:
> I'm writing a little debugger extension and I want to replace the entire
> method source with another string.
>
> I thought of two ways:
>
> aDebugger getTextMorph textMorph editor selectAll.
> aDebugger getTextMorph textMorph editor zapSelectionWi
I'm writing a little debugger extension and I want to replace the entire
method source with another string.
I thought of two ways:
aDebugger getTextMorph textMorph editor selectAll.
aDebugger getTextMorph textMorph editor zapSelectionWith: aString.
or
aDebugger getTextMorph textMorph contents:
