On 7/30/05, Phillip Calvin <[EMAIL PROTECTED]> wrote: > Thomas Mills Hinkle wrote: > > > > >mnemonic_manager also handles notebook's and properly. > > I'm not sure if this is really a rule so much as a convenience, but: > > http://developer.gnome.org/projects/gup/hig/2.0/controls-notebooks.html > From the GNOME HIG: > Do not assign access keys to tab labels, as this means you cannot use > those access keys for any other control on /any/ of the notebook pages > without conflict. Even if you are able to assign access keys that would > not conflict, it is better not to as it may be impossible to avoid the > conflict when your application is translated to other languages. Assign > an access key to every other control on each page, however.
Right. My module just reassigns keys as necessary based on the mnemonics you've already set up in glade, so there's no reason using this means you need to put mnemonics on tabs. By "handles properly", I mean that the program checks which page a widget is on before looking for conflicts -- it understands that you can use the same mnemonic for items on different pages of a notebook. That said, since I use this solution to programatically avoid conflicts, it makes it less of a problem to assign keys to tabs. In my app, I've put shortcuts on the tab labels in spite of their suggestion for two reason: 1. I use my mnemonic_manager to avoid conflicts w/o making translator's lives too hard 2. There's no convenient, reliable way to quickly move between tabs from the keyboard. Control-Pageup and Pagedown seems to be the norm, but this fails if you're inside a SpinButton or other widget that grabs these signals. I wish they'd make sure notebook-pages had a unique key command to move between them if they're going to recommend getting rid of mnemonics! Tom _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
