Community
Participate
Working Groups
Build Identifier: M20100909-0800 The IPreferenceConstants interface is internal and therefore it's not recommended to access its constants. But the constant PLUGINS_NOT_ACTIVATED_ON_STARTUP it's necessary in order to find out if the startup of your plugin was deactivated. Reproducible: Always Steps to Reproduce: 1. Import IPreferenceConstants 2. 3.
Is this a request to make the preference API? Why does it matter to your plugin if it is not started with o.e.ui.startup? PW
This is not a request to make the preference API, we only want to have access to this constant. About your other question: in the document "Ready for IBM Rational software Eclipse and Rational Practitioner Products Integration Requirements V7.8.2" there is a requirement (2.11.c) to do so: "2.11.c. If the use of this extension point is disabled by the user (in Window > Preferences > Workbench > Startup and Shutdown) your implementation will detect and handle this condition. It must not regress, misbehave, or crash. Technical note: The following code will return a negative integer if startup has not been disabled by the user for your plug-in: PlatformUI.getWorkbench(). getPreferenceStore().getString( IPreferenceConstants.PLUGINS_NOT_ACTIVATED_ON_STARTUP). indexOf("your plug-in id"); Your plug-in id is in the returned string if early startup for your plug-in has been disabled by the user (non-negative result). Note, a negative integer is returned even if your plug-in does not contribute to the org.eclipse.ui.startup extension point." On the other hand, if there's the possibility to use the startup extension point, it should also be possible to know if the user has deactivated the startup. Carmelo
(In reply to comment #2) > This is not a request to make the preference API, we only want to have access > to this constant. Access to the constant in what way, different from how it works right now? If I put it on a public, non-internal interface like org.eclipse.ui.IWorkbenchPreferenceConstants that makes it API. PW
Oh, sorry, I thought you meant the whole IPreferenceConstants. Of course that would be a possibility, to move PLUGINS_NOT_ACTIVATED_ON_STARTUP to make it API.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
