Eclipse Community Forums: Eclipse 4 » Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor

Home » Eclipse Projects » Eclipse 4 » Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor

Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1137183]

Mon, 14 October 2013 06:09

Eclipse User

I have migrated an e4 RCP application to the most recent Kepler 4.3.1 release.

The RCP application has dependencies to org.eclipse.ui and therefore also to org.eclipse.ui.workbench.

While doing a regression test after switching to the 4.3.1 target platform, I noticed that key bindings defined in the e4 application model were broken.

I tracked the problem down to the org.eclipse.ui.internal.BindingToModelProcessor which deletes all key bindings which do not have the tag "type:user". This includes also the bindings defined by my e4 application model.

This behavior has been introduced by a fix to bug 406003 (sry, can't post eclipse links because of forum restrictions).

The attachment contains the e4 sample application project (modification: added org.eclipse.ui dependency) that demonstrates the problem. Just startup the application in Kepler 4.3.1 and try to open the about dialog (CTRL+A) -> the key binding won't work.

Is this new behavior for e4 RCP applications intended? If so, how to correctly define key bindings in the e4 application model?

Attachment: brokenBindingsSampleApplication.zip
(Size: 16.25KB, Downloaded 312 times)

[Updated on: Mon, 14 October 2013 09:40] by Moderator

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1140219 is a reply to message #1137183]

Wed, 16 October 2013 03:55

Eclipse User

Problem is even worse. The removal of key bindings affects all plugins in an application. Even the Live Editor cannot be opened anymore.

PS: I also noticed that tracing key bindings doesn't work. Perhaps this is connected.

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1143549 is a reply to message #1140219]

Fri, 18 October 2013 05:04

Eclipse User

So no one knows how to do it correctly? Certainly adding the tag "type:user" to the key binding can not be a proper solution. It works quite good but it seems to be a misusage of the "type:user" tag, as it should be used for user defined key bindings.

Should I file this as a bug?

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1245788 is a reply to message #1143549]

Fri, 14 February 2014 04:12

Eclipse User

Was this ever filed as a Bug?

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1264593 is a reply to message #1245788]

Wed, 05 March 2014 05:44

Eclipse User

Please file a bug on https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform&component=UI

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1426512 is a reply to message #1264593]

Thu, 18 September 2014 17:42

Eclipse User

I've created a workaround using a custom model processor that simply adds the tag "type:user" to all key bindings, see this Gist:
gist.github.com/mbackschat/21b6d2254f1eb962fa50

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1708544 is a reply to message #1426512]

Thu, 17 September 2015 07:38

Eclipse User

The bug is https://bugs.eclipse.org/bugs/show_bug.cgi?id=461037

Re: Kepler SR 1 (4.3.1): e4 key bindings will be removed by BindingToModelProcessor [message #1737156 is a reply to message #1137183]

Wed, 06 July 2016 03:39

Eclipse User

How can I get the workaround for the CSS Spy Editor?
My own key bindings work now, since using the "type:user" tag.

Previous Topic:	TERRIBLE update to Neon
Next Topic:	Updated target platform to Eclipse Neon (4.6) and now Placeholder elements require 'ref' attribute

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 16 17:47:20 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter