Re: How to handle Ctrl+C/V/X accelerators?

[Havoc Pennington <hp redhat com>]

On Mon, 2003-09-08 at 10:30, Tommi Komulainen wrote:
> Hi,
>
> How exactly is one supposed to be handling Ctrl+X/C/V accelerators
> (Cut/Copy/Paste) correctly?  The problem is that when those accelerators
> are in the application menus, the menu callbacks seem to have precedence
> over everything else; the menu callback is always fired, overriding the
> normal GtkEntry keybindings altogether.
>
> Are we supposed to check which widget has focus when the menu callback
> is called, and manually call gtk_editable_cut_clipboard() etc. functions
> if the focus is in a GtkEditable?
>
> What about Ctrl+W (standard keybinding for Close, but also delete-word
> in GtkEntry and friends in Emacs keybindings)?  Are we supposed to be
> checking which widget is focused as well as what keybinding-theme the
> user is using?
>
> In our case the menu accelerators are set up by bonoboui, but I've come
> to believe it essentially boils down to how Gtk is handling the
> accelerators.

This will probably work automatically with the new menu system in GTK+
2.4 (or at least will work automatically when entry/textview are fixed
in GTK+ 2.6) but is going to be a world of pain to set up with 2.2.

Havoc