Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360226 - Conflicting key binding Alt+Shift+<letter> causes a lot of flickering
Summary: Conflicting key binding Alt+Shift+<letter> causes a lot of flickering
Status: CLOSED DUPLICATE of bug 346737
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   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: 2011-10-07 08:56 EDT by Markus Keller CLA
Modified: 2011-10-07 10:40 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-10-07 08:56:20 EDT 
3.5.2 and I20111005-0925 on Windows 7 64bit (I've never seen that before, so it could also be a platform-specific issue)

In a new workspace, add 2 conflicting key bindings for Alt+Shift+<letter>. Then press the shortcut.

=> Workbench window borders flicker heavily, and after a short blocking of the UI thread, the conflicts popup appears and goes away again.

One example to reproduce is assigning Alt+Shift+Y to About and Activate Editor.
I encountered this when trying to bind both Git > Show Annotations and CVS > Show Annotation commands to Alt+Shift+A.
Comment 1 Remy Suen CLA 2011-10-07 10:08:30 EDT 
Markus, based on your description, I'm guessing it's the same bug as bug 346737?
Comment 2 Markus Keller CLA 2011-10-07 10:37:19 EDT 
Yes, looks like the same problem, except that I didn't have to do anything to get out of the loop except for waiting for 10 seconds.
Comment 3 Remy Suen CLA 2011-10-07 10:40:07 EDT 
(In reply to comment #2)
> Yes, looks like the same problem, except that I didn't have to do anything to
> get out of the loop except for waiting for 10 seconds.

Yes, that should be it. It will eventually "run to completion". I noticed that later but perhaps never updated the original bug.

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