>Thank you.
>With WParam we got only #10057 and it is ok. No more "range check" errors.
Thanks for your feedback.
10057 can definitely
--
francois.pie...@overbyte.be
Embarcadero MVP
http://www.overbyte.be
http://francois-piette.blogspot.com
be ignored.
--
To unsubscribe or change your sett
Thank you.
With WParam we got only #10057 and it is ok. No more "range check" errors.
We see that in code several places where needed "WParam". Hope you will fix
it in next versions of ICS.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi
> Sometimes client can disconnect on multithreaded server while send,
> after that I receive "Range check error" or "Socket is not
> connected (#10057 in Send)"
SVN for V8 is updated with Francois' cast fix in various PostMessages to avoid
the range check error (some were already cast correctly)
> I see same problem were posted month ago, and Michael Gasser
> found exactly where error occurs, but nobody answered him
> http://lists.elists.org/pipermail/twsocket/2013-November/045736.html
I've just answered this question. Check if this works for you.
> Any way I will make stackTrace with
I see same problem were posted month ago, and Michael Gasser found exactly
where error occurs, but nobody answered him
http://lists.elists.org/pipermail/twsocket/2013-November/045736.html
Any way I will make stackTrace with jclDebug soon (monday)
--
To unsubscribe or change your settings for TWSo
> Sometimes client can disconnect on multithreaded server while send, after
that I receive
> "Range check error" or "Socket is not connected (#10057 in Send)"
> How can I avoid these errors?
> I'm checking client state before send.
> Must I ignore both these errors? If yes, I can understand to ig
