Various aspects of each device may be configured. The easiest way of creating a GUI to allow the user to configure such a device is to use the GtkInputDialog widget in GTK+. **However, even when using this widget, application writers will need to directly query and set the configuration parameters in order to save the state between invocations of the application.** The configuration of devices is queried using gdk_devices_list(). Each device must be activated using gdk_device_set_mode(), which also controls whether the device's range is mapped to the entire screen or to a single window. The mapping of the valuators of the device onto the predefined valuator types is set using gdk_device_set_axis_use(). And the source type for each device can be set with gdk_device_set_source().
From the GTK docs [http:// www.gtk. org/api/ 2.6/gdk/ gdk-Input- Devices. html] (Sentence emphasized with **):
Various aspects of each device may be configured. The easiest way of creating a GUI to allow the user to configure such a device is to use the GtkInputDialog widget in GTK+. **However, even when using this widget, application writers will need to directly query and set the configuration parameters in order to save the state between invocations of the application.** The configuration of devices is queried using gdk_devices_list(). Each device must be activated using gdk_device_ set_mode( ), which also controls whether the device's range is mapped to the entire screen or to a single window. The mapping of the valuators of the device onto the predefined valuator types is set using gdk_device_ set_axis_ use(). And the source type for each device can be set with gdk_device_ set_source( ).
Could this be the problem?