nanogui@linuxhacker.org
nanogui@linuxhacker.org
: Instead of implementing this a server call, probably the easiest way to do
: it is to use setitimer() on the client side and set a flag in the alarm
: handler which causes the main loop to clear the flag and return a
: timeout event instead of simply rescheduling (search for "errno != EINTR"
: in nanox/srvmain.c).
The easiest way to handle this will be to create a new call,
GetNextEventTimeout(), which will use the timeout value
in the client's existing select() code; quite simple. If select()
returns with a timeout, I'll create a GR_EVENT_TYPE_TIMEOUT
and return it from GetNextEventTimeout().
Regards,
Greg
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: nanogui-unsubscribe@linuxhacker.org
: For additional commands, e-mail: nanogui-help@linuxhacker.org
:
:
nanogui@linuxhacker.org