Skip to main content



      Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Keybinding problem after inheriting the eclipse default scheme
Keybinding problem after inheriting the eclipse default scheme [message #516192] Tue, 23 February 2010 01:53 Go to next message
Eclipse UserFriend
Hi All,

I met a problem when using key binding mechanism. In my RCP product I
have to use the accelerate key combination: "M1+N" to open a new editor,
but unfortunately the eclipse UI has already give the default action for
this combination.

So I apply a new scheme for this, and let
org.eclipse.ui.defaultAcceleratorConfiguration be the parentId.

It appears normal when I press Ctrl+N slowly, but when I frequently
press the Ctrl+N several times(without intterrupt), the Original Eclipse
New Wizard shows, its useless for my product.

In my handler, the process is a little slow. I think that's the problem,
for if I removed all the codes in the handler.execute() function,
everything works fine.

I'm confused by this behavior, seems even if the new scheme activated,
the keybindings in the old scheme can still have high priority in some
situation? Does anyone have the idea about this and give me some clue?

Great thanks!
Re: Keybinding problem after inheriting the eclipse default scheme [message #516809 is a reply to message #516192] Wed, 24 February 2010 23:30 Go to previous messageGo to next message
Eclipse UserFriend
Can anyone give me a clue? Thanks!

On 2/23/2010 2:53 PM, nemo.zhp wrote:
> Hi All,
>
> I met a problem when using key binding mechanism. In my RCP product I
> have to use the accelerate key combination: "M1+N" to open a new editor,
> but unfortunately the eclipse UI has already give the default action for
> this combination.
>
> So I apply a new scheme for this, and let
> org.eclipse.ui.defaultAcceleratorConfiguration be the parentId.
>
> It appears normal when I press Ctrl+N slowly, but when I frequently
> press the Ctrl+N several times(without intterrupt), the Original Eclipse
> New Wizard shows, its useless for my product.
>
> In my handler, the process is a little slow. I think that's the problem,
> for if I removed all the codes in the handler.execute() function,
> everything works fine.
>
> I'm confused by this behavior, seems even if the new scheme activated,
> the keybindings in the old scheme can still have high priority in some
> situation? Does anyone have the idea about this and give me some clue?
>
> Great thanks!
Re: Keybinding problem after inheriting the eclipse default scheme [message #523529 is a reply to message #516809] Fri, 26 March 2010 13:29 Go to previous message
Eclipse UserFriend
Hi there,

Can you please share the code fragment of the plugin.xml ?

Regards,
Previous Topic:customise the content of the OutlineView
Next Topic:Increase Heap space using INI file
Goto Forum:
  


Current Time: Tue Jun 24 23:02:18 EDT 2025

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

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

Back to the top