View toolbars and view->Toolwindows should show keyboard shortcuts.

[jporkkahtc]

View toolbars and view->Toolwindows should show keyboard shortcuts.
Most menu items, if there is a keyboard mapping defined, will show this in the menus automatically.
That doesn't work for toolwindows and toolbars -- would really be handy for discovering these keyboard mappings.
The same is probably true for other dynamically generated menus.

[Clark]

View toolbars and view->Toolwindows should show keyboard shortcuts.
Most menu items, if there is a keyboard mapping defined, will show this in the menus automatically.
That doesn't work for toolwindows and toolbars -- would really be handy for discovering these keyboard mappings.
The same is probably true for other dynamically generated menus.

The reason that these key bindings don't show up is because the "toggle-XXX" and "activate-XXX" commands are not being used. The actions are different.

[jporkkahtc]

WRT tool windows: So whats the difference, or intended difference between
    execute('show_tool_window -current-mdi _tbannotations_browser_form');
and

• toggle-annotations-browser()
• annotations-browser()
• activate_annotations()

View toolbars and view->Toolwindows should show keyboard shortcuts.
Most menu items, if there is a keyboard mapping defined, will show this in the menus automatically.
That doesn't work for toolwindows and toolbars -- would really be handy for discovering these keyboard mappings.
The same is probably true for other dynamically generated menus.

The reason that these key bindings don't show up is because the "toggle-XXX" and "activate-XXX" commands are not being used. The actions are different.

[Clark]

The View>Tool Windows menu item is for creating multiple instances so you can dock them to floating windows. Different that activating or toggling. Some case are the same though.