Submitted by Millenniumman on Mon, 06/25/2007 - 22:01.
Should XtAddInput normally be triggered by data that is already written (write()) on a socket when XtAddInput is run, but has not yet been read by anything?
If not, is there any way to do this?
If so, is there anything that would prevent this from happening?
I am trying to get it to do this, but it is not being triggered. It is triggered by the same data if XtAddInput is run beforehand, so the handler is registered before any data is written, but this is not always possible.
This is at the server of the socket, XtAddInput is set to watch the result of an accept() function. A different handler function, set by an earlier XtAddInput call, has already been triggered by a connect(). It calls the XtAddInput in question.
I am aware that the XtAdd* functions are depreciated, but that doesn't seem to be the problem here. Does it?