Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » How to handle key binding conflicts between product dependencies?
How to handle key binding conflicts between product dependencies? [message #1759096] Thu, 06 April 2017 09:35 Go to next message
Jeritiana Ravelojaona is currently offline Jeritiana RavelojaonaFriend
Messages: 1
Registered: April 2017
Junior Member
In the Eclipse RCP product I'm working on, I have two external dependencies which contribute with the same key binding extension (ALT+CTRL+Y) and empty contextIds.
I know if I had to define those key bindings myself, I could have used different contexts to avoid the conflict.
But here, those are dependencies that are already packaged, I can't seemingly change the source code.
Do you have any clue on how to handle this?

Re: How to handle key binding conflicts between product dependencies? [message #1759828 is a reply to message #1759096] Tue, 18 April 2017 09:26 Go to previous message
Brian de Alwis is currently offline Brian de AlwisFriend
Messages: 788
Registered: January 2012
Senior Member

It's buried in the documentation of the org.eclipse.ui.bindings extension point:

If a binding does not define a command identifier, then it is a deletion marker. This means that if all the conditions are met, it will cancel any bindings with the same trigger in the same context. This mechanism can be used, for example, to change a binding on a particular platform.

Eclipse Platform committer. Ask me about Eclipse support, training, and consulting.
Previous Topic:What does line-prefix operation mean?
Next Topic:event.getDelta().getResource()
Goto Forum:

Current Time: Sun Nov 18 10:42:45 GMT 2018

Powered by FUDForum. Page generated in 0.01773 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top