Bug 34397 - [Key Bindings] Reassigning next/previous editor doesn't work as expected
Summary: [Key Bindings] Reassigning next/previous editor doesn't work as expected
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Douglas Pollock CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-10 13:30 EST by John Arthorne CLA
Modified: 2003-09-09 15:54 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2003-03-10 13:30:35 EST
Build: 2.1 RC2

- Reassign the "Next Editor" and "Previous Editor" actions to Ctrl+6 and
Ctrl+Shift+6.

- the next/previous editor popup no longer works in the reverse direction. 
I.e., hold down Ctrl+Shift, and repeatedly hit 6.  The dialog pops up and
disappears on each key press, but the editor does not change.

The same is true for next/previous view/perspective actions.

Note these will be common keys to rebind because the defaults don't work at all
on Motif.
Comment 1 Nick Edgar CLA 2003-03-12 00:18:09 EST
Which desktop were you using?  Ctrl+Fn keys are used for desktop switching in 
KDE.  This is not specific to Motif.

Still, the behaviour here is wrong.
Comment 2 John Arthorne CLA 2003-03-12 10:01:40 EST
Yes, I was using KDE.
Comment 3 John Arthorne CLA 2003-03-19 17:24:33 EST
I think this got worse in RC3.  On Windows, I redefined:

Next editor: Alt+1
Previous editor: Alt+Shift+1

I can no longer cycle through the list past the first item, even in the forward
direction.

1) Depress Alt key
2) Depress and release '1' key

-> Editor list pops up, and it correctly moves to second item in MRU list

3) Depress and release '1' key again

-> It doesn't move to the next item in the list.
Comment 4 John Arthorne CLA 2003-03-19 17:25:16 EST
To be accurate, this was in build 200303182359.  RC3 hasn't been declared yet.
Comment 5 John Arthorne CLA 2003-03-19 17:28:37 EST
Hmm, maybe this is a slightly different bug.  Mapping to Ctrl+2 and Ctrl+Shift+2
works fine forwards, but not backwards.  Mapping to Alt+2 and Alt+Shift+2 does
not work in either forward or backward direction.
Comment 6 Douglas Pollock CLA 2003-08-27 09:06:40 EDT
There are currently some problems with entering certain key bindings on GTK (my
testing platform).  However, I have confirmed that Ctrl+6, Alt+1, Alt+Shift+1,
Ctrl+2, Alt+2, and Alt+Shift+2 all work.  Even with a GTK workaround in place, I
can't bind to Ctrl+Shift+2.  I'll investigate further on Windows XP.
Comment 7 Douglas Pollock CLA 2003-09-09 15:53:51 EDT
Ctrl+Shift+2 currently generates NUL ('\0') on SWT.  We're working with them to
fix this problem.  See Bug 42035 for the most likely solution.

Ctrl+Shift+[0-9a-f] are reserved by GTK for inputting Unicode characters.  See
Bug 42009 for more information.

I don't believe anything other than those two problems is mentioned here that
still doesn't work.  Whether this is a duplicate, fixed or something else is a
philosophical debate.  I say: fixed.