|Issue Related To IExtensionRegistry addContribution [message #843403]
||Fri, 13 April 2012 02:31
| Rob Hatcherson
Registered: July 2009
Location: Fort Worth, TX, USA
I'm working on a RCP app and have bumped into a problem related to IExtensionRegistry.addContribution(...args...). I originally posted to the RCP forum, but I think the folks here might also have some insight into this problem. I apologize if this violates a policy of the forums since it's a multi-post.|
The IDE version I'm using is Indigo on Fedora 12, and says:
Build id: M20120208-0800
As far as I know everything in Eclipse proper is up to date.
The issues are (I'll get to the addContribution part shortly):
1) I have at least one plugin.xml file that makes coolbar contributions, but after the workbench window initially pops up the coolbar remains hidden until the main window is resized horizontally. At that point the coolbar pops in, looks like I expect, and functions normally. This behavior is similar to message www.eclipse.org/forums/index.php/mv/msg/140033/ (sorry, it wouldn't let me make a real link here).
2) That same plugin.xml attempts to make a contribution to the status bar but the contribution never shows up. I set a breakpoint on the contribution's createControl method but it never got hit. So... in this case the contribution seems to be totally ignored.
I'm loading contributions from various plugin.xml files via "interim" public API:
The plugin.xml files being loaded make typical contributions, e.g. views, perspectives, menus/toolbars/etc. Other than the technique being used to load them nothing unusual is going on.
I have an IRegistryEventListener in the loop and it shows the contributions being processed from the plugin.xml, including the status bar contribution that is never realized.
I have at least one other app that loads contributions via the RegistryFactory.getRegistry().addContribution(...args...) method, and its coolbar shows up as soon as the workbench window springs to life though it also exhibits Problem 2) noted above. I'm still looking for what the working app is doing that the broken app might not be doing regarding the coolbar, but so far no revelations.
I've spent a good chunk of the last few days snooping around in TrimContributionManager trying to figure out what's going on, but I am a relative noob on workbench internals and don't yet know what to expect to see at various points as the workbench springs to life. Guidance about what to look for is welcome.
I later discovered that if I made the following call significantly after the workbench window is up (e.g. from a command tied to some menu item) then the status bar contribution is finally created:
I assume this happens because this call triggers a re-layout of the window.
Point being, the contributions are in there somewhere, which we already knew because the IRegistryEventListener showed them being loaded. They just aren't springing to life all the way.
Anybody have any theories about what might be going wrong with contributions loaded through this interim API that would cause either of the problems mentioned above? Limitations, calls I should be making after addContribution() that might be missing, call ordering, etc.?
Powered by FUDForum
. Page generated in 0.01992 seconds