Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
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 Go to next message
Thorsten Hake is currently offline Thorsten Hake
Messages: 2
Registered: November 2012
Junior Member
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?

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

Report message to a 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 Go to previous messageGo to next message
Ralph Schuster is currently offline Ralph Schuster
Messages: 5
Registered: September 2012
Junior Member
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 Go to previous messageGo to next message
Thorsten Hake is currently offline Thorsten Hake
Messages: 2
Registered: November 2012
Junior Member
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 Go to previous messageGo to next message
Stefan Murawski is currently offline Stefan Murawski
Messages: 2
Registered: February 2014
Junior Member
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 Go to previous message
Sopot Cela is currently offline Sopot Cela
Messages: 596
Registered: December 2010
Senior Member

Please file a bug on https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform&component=UI
Previous Topic:No CSS styling in exported Eclipse RCP product
Next Topic:Handler can not search desired class
Goto Forum:
  


Current Time: Tue Jul 29 21:00:23 EDT 2014

Powered by FUDForum. Page generated in 0.02059 seconds