[news.eclipse.platform.rcp] Re: Shortcut problem

[Alex IgnÃcio da Silva <alex@xxxxxxxxxxxxxxx>]

Hi Paul,

Cool, now I managed to override the platform's default bindings!

There was still one tricky step which was setting
org.eclipse.ui/KEY_CONFIGURATION_ID=myscheme in
plugin_customization.ini, as I could find in Lars' tutorials.

Thank you very much for the hints.

Alex

Paul Webster wrote:
> Alex IgnÃÂcio da Silva wrote on Wed, 02 September 2009 13:02
>> I managed to exclude the default shortcut by registering an extension to
>> org.eclipse.ui.bindings with no commandId set, but that disables the
>> shortcut of my custom command too. What I really wanted to do was to
>> override the platform's default shortcut.
> 
> 
> You can override a shortcut in one of 3 ways
> 
> 1) create a new scheme with no parent.  You can then define as many
> keybindings as you want, as you will see none of the  default bindings.
> 
> 2) create a new scheme with the default scheme parent.  You will inherit
> all of the default keybindings, but any that you define in your scheme
> will take precedence (I think :)
> 
> 3) create a child context off of the context containing some of the
> bindings.  Any keys that you define in your context will take precedence
> over the original context.
> 
> PW
>