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

Bug 483227

Summary:	[KeyBindings] Conflicts for keys is not shown
Product:	[Eclipse Project] Platform	Reporter:	Robert Stoll <rstoll>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, kalyan_prasad, lydiaw
Version:	4.5.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Robert Stoll

2015-11-29 07:27:35 EST

Following steps to reproduce the bug:
1. clean install of eclipse with standard key bindings
2. Window -> Preferences -> General -> Keys
3. Enter "Quick Fix"
4. Delete current "Binding:" and enter ALT+Enter

=> no Conflicts are shown

However, the conflict is shown if:

5a. click ok and repeat steps 2 and 3
5b. alternatively, choose "In Windows" instead of "In Dialogs and Windows" for "When"

Expected behaviour:
The conflict is already shown without performing step 5a or 5b

Comment 1 Lydia Woodson

2018-04-19 15:20:38 EDT

I also see this with Eclipse 4.6.3.
Conflicts - key bindings that are already assigned - should be listed in the Conflicts window once the unbind and entry of a new key combination is tested.

Following steps to reproduce the bug:
1. clean install of eclipse with standard key bindings
2. Window -> Preferences -> General -> Keys
3. Enter "split" in the type filter text field
4. See Toggle Split Editor.
4. Delete current "Binding:" and enter ALT+Enter or ALT+V or any binding that is already in use.

=> no Conflicts are shown
They should show in the window when the new key combination is entered.

Expected behaviour:
The conflict should show in the conflicts window.

Comment 2 Dani Megert

2018-09-19 12:34:16 EDT

Looks like context inheritance is not taken into account.

Comment 3 Eclipse Genie

2020-09-09 05:33:51 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.