[wx-dev] Fix for Reentrance problems in events (Sockets problem,
even more?) (Was: Status of the SOC2006_SOCKET branch)
Albert van Peppen
Albert at insad.nl
Fri Oct 6 05:20:17 PDT 2006
Hi all,
I've got my socket problems fixed.
1) After some investigation it turned out that when using event driven
sockets handling, the EventHandler class was called reentrant, which
eventualy causes wxYield() to enter a recursive state.
I did change the eventhandling in such a way that you can specify per
event handler wheter or not it is allowed to be reentrant (although i
cannot see why it should be reentrant, but since this is the old
behaviour i left this to be the default).
This fixes my problem and i can imagine it can fix sever problems with
controls as well (if they are declared non-reentrant).
2) I also have put up a way to set the default timeout value for sockets
because when i start a wxClient session and there is no server available
at that time, the default timeout is set to 10 minutes! (Which is way to
long to report a user that the server is not available)
3) There where various size problems in the low-level stream and skipc
sources. Some i fixed, some are just guarded with an assertion (might be
fixed by someone with more time :)) The assertions are in place but
after i fixed some forgotten initializations the did not occour anymore.
Should i post a patch for these issues? And if so, how is the best way;
against latest head or against 2_6 branch?
Regards,
Albert van Peppen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wxwidgets.org/pipermail/wx-dev/attachments/20061006/aa2c83e6/attachment.htm
More information about the wx-dev
mailing list