Input
Callbacks on file descriptors
The functions in this section are used to establish
callbacks when some condition becomes true for
a file descriptor. They are currently just wrappers around
the IO Channel
facility.
GLib Main LoopThe main loop in which input callbacks run.IO ChannelsA newer and more flexible way of doing IO
callbacks.
@source:
@condition:
@function:
@data:
@destroy:
@Returns:
A set of bit flags used to specify conditions for which
an input callback will be triggered. The three members
of this enumeration correspond to the @readfds,
@writefds, and @exceptfds arguments to the
select system call.
@GDK_INPUT_READ: the file descriptor has become available for reading.
(Or, as is standard in Unix, a socket or pipe was closed
at the other end; this is the case if a subsequent read
on the file descriptor returns a count of zero.)
@GDK_INPUT_WRITE: the file descriptor has become available for writing.
@GDK_INPUT_EXCEPTION: an exception was raised on the file descriptor.
A callback function that will be called when some condition
occurs.
@data: the user data passed to gdk_input_add() or gdk_input_add_full().
@source: the source where the condition occurred.
@condition: the triggering condition.
A callback function called when a piece of user data is
no longer being stored by GDK. Will typically free the
structure or object that @data points to.
@data: the user data.
@source:
@condition:
@function:
@data:
@Returns:
Remove a callback added with gdk_input_add() or
gdk_input_add_full().
@tag: the tag returned when the callback was set up.