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

Bug 124959

Summary: [Commands] handlers: Usability problem with Next Editor dialog on Linux
Product: [Eclipse Project] Platform Reporter: Sergey Prigogin <eclipse.sprigogin>
Component: UIAssignee: Douglas Pollock <douglas.pollock>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 Keywords: helpwanted
Version: 3.1.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:

Description Sergey Prigogin CLA 2006-01-23 19:01:03 EST 
When Next Editor dialog is brought up using the default Ctrl-F6 shortcut, it is hard to select any item other than the initially selected second one. If I press Up/Down arrow keys while holding Ctrl, the selection does not move. If I release the Ctrl key before pressing any arrow keys, the default second item gets selected. The only way, I found, that kind of works is to press an arrow key at least once while holding the Ctrl key, then release the Ctrl key and continue pressing arrow keys to navigate to the desired item. If I need the third item in the list, I have to press Ctrl-Down, Down, Up to get it selected. This is a counter intuitive and three times longer keystroke than s single Ctrl-Down that achieves the same result on Windows.
Comment 1 Douglas Pollock CLA 2006-01-24 10:45:45 EST 
(1) You can continue to press Ctrl+F6 (and Ctrl+Shift+F6) to move the selection.
(2) You can go into "Window > Preferences > General", and select "Keep next/previous part dialog open".  Then release both Ctrl and F6, and use the arrow keys.
(3) After the first arrow press, you can release the Ctrl key.  Subsequent arrow presses will move the selection.  The problem here is that the native table has a concept of selection and focus.  With Ctrl depressed, only the focus row changes.  You have to release Ctrl to move the selection.  It is challenging to workaround this native behaviour, and (1) and (2) provide good alternatives.

So, I don't see that it is worth it to try to workaround the native behaviour in this case.
Comment 2 Douglas Pollock CLA 2006-01-24 10:46:28 EST 
If you (or someone else) is willing to provide a patch, I will consider it for inclusion.  Otherwise, I'm closing as WONTFIX.