Well, we can enforce no conflicts without going through a third party,
right? The UI enforces no conflicts, and the library checks that a
keybinding is not already taken at bind time (allowing the app to prompt
the user if it is).
It isn't as though a third party gives any better form of conflict
avoidance... apps can still bind using X manually, which is what is done
today.
-Alex
Mark McLoughlin wrote:
On Thu, 2005-06-16 at 11:57 -0700, Alex Graveley wrote:
I think the global binding problem can be solved by just designating a
GConf path that apps install a keybinding action into. Then create a
library with tomboykeybinder.c that apps call into with the GConf paths
they are interested in. The library reads the GConf binding keys for
the app and registers the X root window event handler.
Hold on, isn't the main issue here that you want a single X client to
be responsible for all the global keygrabs in order to avoid conflicts?
A convenience API seems kinda secondary ...
(We fixed this in the panel by moving the shortcuts to metacity and
adding a ClientMessage protocol which metacity uses when the shortcuts
are invoked)
Cheers,
Mark.
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
