Thanks for this, and for responding to the SO question. I'll see if I
can rewrite the run async abstraction using your solution.


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 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 you want to see this technique in action:
> I have implemented both the busy wait (reactOnEventTimer) and the
> event-driven method (reactOnEvent).

How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.;262219672;13503038;z?
wxhaskell-users mailing list

Reply via email to