joseluis
16th June 2015, 13:16
Hi.
If you are processing a readyRead slot and new information is received, you will not be inform about it. It looks logical...
http://stackoverflow.com/questions/16023533/how-to-make-sure-that-readyread-signals-from-qtcpsocket-cant-be-missed
Is it possible that an exception thrown inside of readyRead slot, and captured on QApplication::notify the socket thinks my application continues inside readyRead slot?
To solve it, I only need to add a try catch on readyRead slot.
It looks confusing and not enough documented.
I suppose, that Qt cannot manage the situation because the slot could be thrown to a different thread. Is that right?
kind regards
If you are processing a readyRead slot and new information is received, you will not be inform about it. It looks logical...
http://stackoverflow.com/questions/16023533/how-to-make-sure-that-readyread-signals-from-qtcpsocket-cant-be-missed
Is it possible that an exception thrown inside of readyRead slot, and captured on QApplication::notify the socket thinks my application continues inside readyRead slot?
To solve it, I only need to add a try catch on readyRead slot.
It looks confusing and not enough documented.
I suppose, that Qt cannot manage the situation because the slot could be thrown to a different thread. Is that right?
kind regards