Hello, I find there are more menu and toolbar contributions through org.eclipse.ui.menus and org.eclipse.ui.commands extension points do not work in eclipse 4.2 M4 in compared to 4.2 M3, which already have a certain set of contributions through these extension points not working in compared to 3.7.x.
I listed some examples in the email below. Take an example in org.eclipse.debug.ui plugin, the watch command org.eclipse.debug.ui.actions.WatchCommand and handler org.eclipse.debug.internal.ui.actions.expressions.WatchHandler. When I select a variable in Variables View and bring up its context menu, I see the watchHanlder is being called on methods like isEnabled, but I do not see the context menu item 'Watch' comes up in the context menu. This also happens to the variables view when I use eclipse 4.2 SDK to debug a java project. So I think it is a general issue. Is it just broken in M4 that will be fixed in M5? Or is it an intent to start cutting the functionality of the compatibility layer for the release of 4.2? Thanks, Winnie From: [email protected] [mailto:[email protected]] On Behalf Of Lai, Winnie Sent: Friday, January 13, 2012 1:16 PM To: [email protected] Subject: [cdt-dev] cdt dsf on eclipse 4.2 Hello, I am trying eclipse EPP CPP package 4.2 M3 and M4 and compare them with eclipse 3.7.1. I find some dsf view commands are missing and some toolbar commands enable/disable state are not proper. Here are some examples of the issues, - 3.7.1 has view's pull down menu 'Number Format' and 'Update Policy' in expression / registers / variables view. However, 4.2 M3 does not have 'Update Policy' though it has 'Number Format', while 4.2 M4 does not have both 'Number Format' and 'Update Policy'. - 3.7.1 has context menu item 'Watch' in those views, but 4.2 M4 does not have the menu item. - 3.7.1 variables view toolbar button has disabled state for add/remove/remove all global buttons, which is what I expected. However, 4.2 M3 and M4 have those buttons enabled, and once I click on them, they get disabled. Does anyone see similar issues on these views or other debug related views? Would they be related to e4 compatibility layer as to command-handler mechanism? Thanks, Winnie
_______________________________________________ cdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
