Whats coming in GTK+ 2.12, part 3

["Matthias Clasen" <matthias clasen gmail com>]

Changes related to keyboard navigation and Drag-and-Drop:

Keyboard navigation has seen quite a bit of work this cycle;
with an eye towards consistent handling of keynav failures and
better support for platforms with no or very poor keyboards,
like the Maemo platform, or phones. Since much of this is
about adapting GTK+ to the platform it runs on, you'll see
a lot of settings in the following.

The display of accelerators and mnemonics can be turned
off using the gtk-enable-accels and gtk-enable-mnemonics
settings.

The gtk-keynav-cursor-only setting should be turned on
in environments without the Tab or Shift keys. If it is set,
GTK+ works hard to make everything reachable with just
the arrow keys.

The gtk-keynav-wrap-around controls the wrapping behaviour
of keynav in a number of widgets, e.g. menus and notebooks.

Stopping the cursor blinking in entries (e.g on the login
screen !) and text views during long periods of inactivity
helps to avoid context switches and save power. GTK+ has
had a gtk-cursor-blink setting which simply turns off blinking
for a long time. With 2.12, gtk-cursor-blink-timeout lets
you control how long the text cursor blinks.

Failed keyboard navigation and input errors (e.g. if the user
presses an invalid key) are handled consistently now, by
causing a beep. This can be controlled by the gtk-error-bell
setting. Widget implementations should use the functions
gtk_widget_error_bell() and gtk_widget_keynav_failed() to
participate in the consistent handling of keyboard navigation
and input errors.

When a Drag-and-Drop operation fails for some reason, GTK+
displays an animation moving the drag cursor back to the source
of the drag. In some situations (e.g. with notebook tab DND)
this animation is not appropriate, and the ::drag-failed
signal has been added to GtkWidget to allow handling failed
drags differently.