GTK v1.2 Tutorial: Timeouts, IO and Idle Functions

Next Previous Contents

## 17. Timeouts, IO and Idle Functions

## 17.1 Timeouts

You may be wondering how you make GTK do useful work when in gtk_main. Well, you have several options. Using the following function you can create a timeout function that will be called every "interval" milliseconds.

> `

>     gint gtk_timeout_add( guint32     interval,
>                           GtkFunction function,
>                           gpointer    data );

> `

The first argument is the number of milliseconds between calls to your function. The second argument is the function you wish to have called, and the third, the data passed to this callback function. The return value is an integer "tag" which may be used to stop the timeout by calling:

> `

>     void gtk_timeout_remove( gint tag );

> `

You may also stop the timeout function by returning zero or FALSE from your callback function. Obviously this means if you want your function to continue to be called, it should return a non-zero value, i.e., TRUE.

The declaration of your callback should look something like this:

> `

>     gint timeout_callback( gpointer data );

> `

## 17.2 Monitoring IO

A nifty feature of GDK (the library that underlies GTK), is the ability to have it check for data on a file descriptor for you (as returned by open(2) or socket(2)). This is especially useful for networking applications. The function:

> `

>     gint gdk_input_add( gint              source,
>                         GdkInputCondition condition,
>                         GdkInputFunction  function,
>                         gpointer          data );

> `

Where the first argument is the file descriptor you wish to have watched, and the second specifies what you want GDK to look for. This may be one of:

- `GDK_INPUT_READ` - Call your function when there is data ready for reading on your file descriptor.
- >`GDK_INPUT_WRITE` - Call your function when the file descriptor is ready for writing.

As I'm sure you've figured out already, the third argument is the function you wish to have called when the above conditions are satisfied, and the fourth is the data to pass to this function.

The return value is a tag that may be used to stop GDK from monitoring this file descriptor using the following function.

> `

>     void gdk_input_remove( gint tag );

> `

The callback function should be declared as:

> `

>     void input_callback( gpointer          data,
>                          gint              source,
>                          GdkInputCondition condition );

> `

Where `source` and `condition` are as specified above.

## 17.3 Idle Functions

What if you have a function which you want to be called when nothing else is happening ?

> `

>     gint gtk_idle_add( GtkFunction function,
>                        gpointer    data );

> `

This causes GTK to call the specified function whenever nothing else is happening.

> `

>     void gtk_idle_remove( gint tag );

> `

I won't explain the meaning of the arguments as they follow very much like the ones above. The function pointed to by the first argument to gtk_idle_add will be called whenever the opportunity arises. As with the others, returning FALSE will stop the idle function from being called.

Next Previous Contents