Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 32586 - [Key Bindings] Keys, commands and conflicts
Summary: [Key Bindings] Keys, commands and conflicts
Status: RESOLVED DUPLICATE of bug 33161
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Chris McLaren CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-23 09:35 EST by Darin Swanson CLA
Modified: 2003-03-05 17:21 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Swanson CLA 2003-02-23 09:35:30 EST
It seems to be not possible to determine how to resolve a conflict or if you 
are creating one when assigning a key binding.

Steps:
Selected the command "Show in Package Explorer" for the Standard configuration.
<no key sequences assigned>
Set scope to global
Configuration standard
Selected F9 for key sequence

I have the FollowHyperLink assigned to F9 previously and this shows in the 
commands listing.
I click add.
There is no indication of conflict and it looks like I have been successful in 
setting F9 for Show in Package Explorer (and removing it from FollowHyperLink).
I try to use the Key...nothing.
Back into the preferences
Select Show In Package Explorer

Now it shows a conflict but I do not have indication of with what?

In the commands listing it has <undefined><conflict>?

How do I figure out what the conflict is with?

Clicking remove for this command (Show In Package Explorer), leaves me with 
nothing showing for F9
Comment 1 Chris McLaren CLA 2003-03-05 17:21:58 EST
this was a major problem in RC1. your test case works fine now, and there are 
no conflicts in the factory ship (and you can't introduce them in the 
preference page either). 

'proper' conflicts are still possible (two third-party plugins registering the 
same key for the same scope and configuration, and i am adding a duplicate 
notation to follow resolution of conflicts in the UI

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