Re: [wxhaskell-users] Stop do not stop; not multi-threaded?

[Arthur v. L. <art...@cs...>]

On 18-feb-2007, at 21:58, Eric Y. Kow wrote:

> Hi,
>
> On Mon, Feb 05, 2007 at 16:17:41 -0000, Jos=E9 Miguel Vila=E7a wrote:
>> In theory this seems the solution but when I tested it I find out =20
>> that it
>> doesn=92t. The very long computation gets the attention of the =20
>> processor and
>> blocks the graphical interface; clicking the Stop button don=92t =20
>> fire the
>> actions.
>
> Does calling wxcAppSafeYield in your long computation (look in the =20
> index
> of the API) help?  I don't actually know the answer, just making some
> guesses.  You might want to look into what Dazzle/XTC do, otherwise.

Just as a heads-up: Dazzle doesn't solve this problem at all. Long =20
computations
are split in parts, the (lazy) evaluation of which is driven from the =20=

UI, but any truly
long evaluation will still block the UI.

Doei, Arthur.

--=20

   /\    / |       art...@cs...       | Work like you don't need =20=

the money
/__\  /  | A friend is someone with whom | Love like you have never =20
been hurt
/    \/__ | you can dare to be yourself   | Dance like there's nobody =20=

watching