On Fri, Sep 02, 2011 at 15:55:07 +0100, maciek.makow...@gmail.com wrote:
> If the only restriction here is that all the GUI updates should happen
> on the main OS thread, doesn't it mean that Haskell (green) threads
> spawned through forkIO are fine, because they execute on the same OS
> thread? Or
If the only restriction here is that all the GUI updates should happen
on the main OS thread, doesn't it mean that Haskell (green) threads
spawned through forkIO are fine, because they execute on the same OS
thread? Or does wxHaskell introduce additional restrictions?
Maciek
On Fri, Sep 2, 2011 a
On Fri, Sep 02, 2011 at 15:03:28 +0100, maciek.makow...@gmail.com wrote:
> There is indeed a claim in wxHaskell FAQ that it is incompatible with
> Haskell threads. I have, however, used threads spawned with forkIO to
> update wxHaskell GUI in toy apps, without any ill effects. Examples:
>
> http:/
There is indeed a claim in wxHaskell FAQ that it is incompatible with
Haskell threads. I have, however, used threads spawned with forkIO to
update wxHaskell GUI in toy apps, without any ill effects. Examples:
http://mmakowski.com/wiki/tech:haskell_mvc
https://github.com/mmakowski/habaz
I'd be int
Bonjour List !
I am writing a program that is supposed to listen to a tcp port, and
when a client connects,
update a UI done with wxHaskell.
Since wxHaskell is not compatible with multiple threads, I am not sure
how to do this.
an idea I have is to
- forkOS a thread which will do the network pa
