Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 413758 - Keys in a sequence won't work unless the keys are pressed very quickly together
Summary: Keys in a sequence won't work unless the keys are pressed very quickly together
Status: CLOSED DUPLICATE of bug 369860
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-25 12:50 EDT by David M. Karr CLA
Modified: 2013-07-25 13:04 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 David M. Karr CLA 2013-07-25 12:50:18 EDT
In Indigo, I had numerous commands bound to key sequences of more than one key, mostly only two.

If I start one of the sequences, but don't complete it quickly, Eclipse brings up a dialog showing the commands that are bound to sequences that begin with what I've entered so far.  If I then continue the sequence at that point, it will execute the command bound to that entire sequence.

I'm trying to do the same thing in Kepler, but I've noticed some odd behavior with these multi-key sequences.

If I quickly press the entire sequence, it usually works.  I'm still seeing cases where it seems like nothing happens, but it usually works.

If I delay long enough after starting the sequence, Kepler brings up the same commands list as I saw in Indigo, but if I press the next key in the sequence, it just dismisses the dialog.

I've even seen a different scenario, where I delay a "little bit" between keys, but not enough for it to bring up the commands dialog.  When that happens, that next key goes directly to the view that has focus, which is usually the text editor.  For instance, if my key sequence is "ctrl-x 2", I've often seen it insert the "2" directly into the editor.
Comment 1 Paul Webster CLA 2013-07-25 13:04:24 EDT

*** This bug has been marked as a duplicate of bug 369860 ***