Re: No more font.wait()?

On 10/04/2004, at 5:19 PM, Adam Megacz wrote:
>> My problem was: I had one thread change the position of a cursor, then
>> instance another thread that created the selected region.
>
> Bad.  If you want two things to appear simultaneously, you must do
> them in the same thread without doing any blocking-things in-between.

Yep. I've been thinking about it, and I think it was a special case 
where trap-based designing fell down because of font.wait().

There's no other situation I can think of where this would pop up 
again, so as long as those three points are well documented in the ref, 
no worries.

-- d