Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 151444

Summary:	[Perspectives] Arrow keys in Next Perspective (Ctrl-F8) dialog don't work properly
Product:	[Eclipse Project] Platform	Reporter:	Karl Trygve Kalleberg <karltk>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	trivial
Priority:	P5	CC:	psuzzi, remy.suen
Version:	3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Karl Trygve Kalleberg

2006-07-21 13:59:10 EDT

When using the Next Perspective popup menu (Ctrl-F8), using the arrow keys to select the desired perspective is cumbersome. 

On XP, the popup menu behaves as follows: hit Ctrl-F8 and hold down Ctrl while selecting the desired entry using the up/down arrows, then release Ctrl, and the selected perspective will be activated. 

On Linux, after activating the Next Perspective popup menu with Ctrl-F8, holding down Ctrl while using arrow up/down will not change the selection, but only move the list cursor. Once the list cursor has moved at least once, Ctrl can be released, and the arrow keys must then be used to move the selection (even if the cursor is at the desired perspective, the selection will not be changed from the initial suggestion until an additional move is made). Hitting Enter will activate the selected perspective. 

(Iterating through the alternatives by holdning down Ctrl and repeatedly hitting F8 works as expected. Holding Shift+Ctrl and hitting F8 will move in the reverse direction, as expected.)

Is there any chance that the behaviour on Linux can be corrected to work like the one on XP, which after all, is much more convenient?

Comment 1 Paul Webster

2006-09-28 15:18:09 EDT

Is this still a problem in 3.3?

PW

Comment 2 Denis Roy

2007-06-22 09:33:29 EDT

Changes requested on bug 193523

Comment 3 Remy Suen

2007-08-31 17:00:46 EDT

(In reply to comment #1)
> Is this still a problem in 3.3?

This is still a problem on 3.4M1 for me anyway.

Comment 4 Eclipse Genie

2020-06-19 15:08:58 EDT

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.