Re: No more font.wait()?

Yeah, I file this in the same category as "kernel memory is not swappable".

  - a

David Crawshaw <[email protected]> writes:
> 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
>
>
> _______________________________________________
> core mailing list
> [email protected]
> http://lists.xwt.org/listinfo/core
>

-- 
"It's lucky," he added, after a pause, "that there are such a lot of
islands in the world.  I almost envy you, Mr. Watson."

                                                   -- Mustapha Mond