Comment 1 Darin Wright 2009-01-29 10:18:54 EST

The action is enabled in my target (self-hosting) worksace, but not in my host. Using the shortcut "Alt-Enter" in the debug view will sometimes open the properties dialog even though the action is disabled. Moving to workbench for comment. All we do is contribute a couple property pages:

for org.eclispe.debug.ui:

   <extension
         point="org.eclipse.ui.propertyPages">
      <page
            name="%processPropertyPageName"
            class="org.eclipse.debug.internal.ui.preferences.ProcessPropertyPage"
            id="org.eclipse.debug.ui.properties.process">
         <enabledWhen>
            <or>
               <adapt
                     type="org.eclipse.debug.core.model.IProcess">
               </adapt>
               <adapt
                     type="org.eclipse.debug.core.model.IDebugElement"></adapt>
            </or>
         </enabledWhen>
      </page> 


and from org.eclipse.jdt.debug.ui:


     <page
            class="org.eclipse.jdt.internal.debug.ui.propertypages.VMCapabilitiesPropertyPage"
            id="org.eclipse.debug.ui.properties.vmCapabilities"
            name="%vmCapabilitiesPageName"
            >
         <enabledWhen>
             <and>
                <or>
                   <instanceof
                         value="org.eclipse.debug.core.model.IDebugElement">
                   </instanceof>
                   <instanceof
                         value="org.eclipse.debug.core.model.IProcess">
                   </instanceof>
                </or>
             	<test
                    property="org.eclipse.debug.ui.getModelIdentifier"
                    value="org.eclipse.jdt.debug"/>
                <not>
                   <test
                         property="org.eclipse.debug.ui.isTerminatedOrDisconnected">
                   </test>
                </not>
             </and>
         </enabledWhen>
      </page>

Comment 2 Eclipse Webmaster 2019-09-06 16:14:48 EDT

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.