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).

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
wxhaskell-users mailing list

Reply via email to