Paul McNett wrote:
> Uwe Grauer wrote:
>> Another thing to think about is if a Hotkey has to be the same for every 
>> language. There are quite some standard hotkeys but sometimes hotkeys 
>> are not the same for every language.
>>
>> Maybe this was one of the reasons for having the hotkey in the menutext.
> 
> This is actually a good point, something to think about. When localizing 
> a menu entry and the Caption defines both the caption and the hotkey, it 
> would be easy to set up the hotkey appropriately since it is part of the 
> same string. With hotkey separate, it'll appear in the translation file 
> with no context.
> 
> Is this what you mean?
> 
> I actually think there's another issue, too. I believe HotKey is 
> misnamed. HotKeys in my mind are the underlined characters that you can 
> push to activate that menu item when the menu is opened. Accelerators 
> are the sequences like Ctrl+O which will activate the menu item when the 
> menu isn't even opened.
> 
> So I think we need to rename "HotKey" to "Accelerator", and note that we 
> still support hotkeys in menu captions by using the common & character.
> 
> So:
> 
> men.Caption = "&Open"
> men.Accelerator = "Ctrl+O"
> 
> would result in the menu item having an underlined O, and Ctrl+O being 
> the accelerator.
> 
> Thoughts on this? Sorry for hijacking your point, Uwe.
> 
> Paul

This wasn't hijacking.
My point was just that there is a reason for having the "Hotkey" as part 
of the menutext.
But you are right. There is more than the notion of a Menuhotkey.

It would be nice to have a table of the possibilities in the different
gui frameworks in terms of "Hotkey" support.
This way we had something to think about for what Dabo wants to support
and how to do this.

Uwe


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]

Reply via email to