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 at 3:21 PM, Eric Y. Kow <eric....@gmail.com> wrote: > 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://mmakowski.com/wiki/tech:haskell_mvc >> https://github.com/mmakowski/habaz >> >> I'd be interested to learn how the incompatibility can manifest itself >> -- if there indeed is any. > > It's worth noting this entry from the wxWidgets FAQ: > > wxWidgets (like most GUI toolkits underneath it) is not thread-safe, and > handling of GUI components should always be done exclusively in the main > thread. > > This doesn't stop you from doing the non-GUI stuff in other threads > though. > > Was interested to see that the wxHaskell mutable var is just a TVar > (from STM?) > > -- > Eric Kow <http://erickow.com> > ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ wxhaskell-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
