I've noticed that wxHaskell seems to buffer or synchronise component updates.
That is, if I have something along the lines of:
on command := set w1 ... >> grind, grind >> set w2 ...
then I don't see the update to w1 until it's all done. It doesn't seem to be a
strictness issue: if I interleave the GUI ops with stdout, waits, and system
call, those all seem to happen lazily, and the GUI updates in batch, at the end.
I assumed I could alter this behaviour with "refresh", or else with "repaint",
but those don't seem to have an discernible effect. Is there a a simple way to
change this, or do I need to entirely restructure, to introduce explicit
asynchrony?
My installation is Fedora 10/GNOME, should there be any platform-dependence.
Sorry if this is covered in the documentation, or based on some fundamental
confusion as to how the toolkit's intended to work, but I'm somewhat stuck at
this point, and haven't turned up anything in the docs or on the web.
Cheers,
Alex.
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
wxhaskell-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
