[Sawtooth G4]

Okay, I've got an NSThread batch processing some stuff...
It is displayed nicely inside of a sheet attached to the main window. Everything works nicely, except sometimes (randomly) when I update the NSTextView with different text, it doesn't erase the previous text. It draw right on top of it, resulting in unreadable text.

Is there some trick to alleviating this problem? It doesn't make any sense to me.

[fitter]

What calls are you using to the NSTextView? Are you clearing the field first before writing to it?

I generally do something like:

<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>
[ aTextView setString: <font color = orange>@""</font> ];
[ aTextView insertText: myString ];
</font>[/code]

which clears the field entirely, and then writes to it, rather than replacing one string with another.

[Apocalypse]

I don't know how NSTextViews handle threading but you might want to try using an NSLock around the code that modifies the text view. Any time you are using multiple threads you should use lock objects to protect the API-level code. This is due to the fact that much of the API (the Application Kit especially) is not thread-safe.

Try that and tell us if it fixed the problem.
Jeff.

[Angus_D]

Any code that modifies the UI should probably happen from the main thread. See the TrivialThreads example on ADC Sample Code.