Thanks for the info; I managed to diagnose what was going on: the event
handler for my wxSocketClient was getting cleaned up accidentally, since
apparently you have to create one explicitly to handle events with that
object.
As an aside, is there any known reason why wxSocketBase shouldn't derive
from wxEvtHandler? That choice doesn't entirely make sense to me.
Thanks all,
Evan
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
