Hi Stef,

Did you try the "third" way of showing debug data to the user?
i.e.
String>>displayAt: aPoint
I think this is the way with the least impact on overall behavior
and it avoids any risk of enless recursion and so on...

HTH,
Torge
Am 04.12.2002 20:48:07 schrieb Stephane Ducasse <ducasse at iam.unibe.ch>:

>Hi
>
>I just to report a really strange bug nathanael and I encountered 
>regardings the refreshing
>of the screen on mac. Nathanael implemented a double-buffering for my 
>turtle and it worked really well on pc but on mac we got the problem 
>that all the widgets were refreshed
>  even when they should not have.
>
>We could never identify a reproduceable snippet to submit it to the 
>list, this was really vicious
>because this was in the middle of the different processes interacting 
>so it was extremely plainfull to debug because any change was changing 
>the behavior (no halt, no transcript show allowed).
>
>So if somebody see that this is happening. Believe us. We were amazed 
>that the same code was not running the same way on mac and pc.
>
>Stef
>
>
>
>On mercredi, décembre 4, 2002, at 05:57  pm, Ned Konz wrote:
>
>> On Wednesday 04 December 2002 08:51 am, Bergel Alexandre wrote:
>>
>>> I have a subclass of Morph, on which I redefine the method drawOn:
>>> Body of drawOn: is influenced by external event, such as the key,
>>> how can I make the morph refreshed ? Morph>>repaint, Morph>>update,
>>> ... seems to be hided using fancy name...
>>
>> Morph>>changed will invalidate the area of the Morph, causing it to be
>> redrawn soon.
>>
>> There is also layoutChanged, which will force the layout to be updated
>> (and the Morph redrawn).
>>
>> -- 
>> Ned Konz
>> http://bike-nomad.com
>> GPG key ID: BEEA7EFE
>>
>>
>>
>Dr. Stéphane DUCASSE (ducasse at iam.unibe.ch) 
>http://www.iam.unibe.ch/~ducasse/
>  "if you knew today was your last day on earth, what would you do
>  different? ... especially if, by doing something different, today
>  might not be your last day on earth" Calvin&Hobbes
>
>
>
>