Community
Participate
Working Groups
I20090331-0901 The "Customize Perspective" dialog does not allow me to hide items in the "Show In" menu. I tried to remove the new "Show In > Properties" item (since it blocks "Alt+Shift+W, P" from executing "Show In > Package Explorer"). The dialog could just show the currently visible items (they are already enumerated in the tooltip), and when I uncheck an item, add it to a list of items that should not be shown.
Taken for itself, this bug is an enhancement request. But in the SDK, the new "Show In > Properties" actually turns this into a regression, since it effectively removed a key binding for me with no way to get the old behavior back.
Markus/Paul, any idea how it used to work? I always get more than one possibility when I bring up the 'Show in' cascade, how were we picking Package Explorer in the key binding? I'm just wondering if we have accidentally copied the keybinding during the definition of the 'Properties' entry...
There's no default key binding for the "Show In > Package Explorer" command (but yes, I could bind it to e.g. Alt+Shift+E). The "Alt+Shift+W, P" I mentioned was actually - "Alt+Shift+W" to open the "Show In" quick menu - "P" to select the "Package Explorer" This worked (at least on Windows), because none of the items in the "Show In" menu has a mnemonic, and in that case, Windows behaves as if the first character of each menu item was a mnemonic. Before "Show In > Properties" came to life, the Package Explorer was the only view in the Java and Debug perspectives whose name started with "P", so it was unique by coincidence. So, there's nothing wrong with the key bindings story. But there's a usability issue for which there are a few possible solutions: - allow me to disable certain views in the Show In menu (my initial request) - assign mnemonics to the menu items: - add numbers like for the recently opened files in the File menu, or - invent unique mnemonics for views (I don't have a good idea how mnemonics could be assigned in a predictable way)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
