Thanks for this, and for responding to the SO question. I'll see if I
can rewrite the run async abstraction using your solution.
Cheers,
Maciek
On Wed, Sep 26, 2012 at 8:30 AM, Henning Thielemann
wrote:
>
> On Wed, 26 Sep 2012, Henning Thielemann wrote:
>
>> However, it seems to be essential wha
On Wed, 26 Sep 2012, Henning Thielemann wrote:
> However, it seems to be essential what eventId you use. The value in the
> above example (wxID_HIGHEST+1) was already used in my system and this lead
> to strange behavior. I think wxhaskell should provide support for finding
> free event ids.
If
On Wed, 26 Sep 2012, maciek.makow...@gmail.com wrote:
> Including wxhaskell-users. Anyone interested in async UI update functionality?
Am I right that the solution on StackOverflow uses a busy-wait using the
Wx Timer? I think this is a bad idea and I found a better solution at:
http://snipp