As already mention in its help documentation, ClientTCPRead function may return without reading all data you want.
So an example code is provided so one can do the read operation as expected.
But I think this behaviour is not intuitive and I am sure many people (including me) have struggled to much before finding the cure.
I suggest to add a second function to the TCP library like ClientTCPReadExact which does this workaround for us and returns with all the data we have asked for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.