Description Darin Wright 2007-02-19 15:24:07 EST

Using I20070213-0907, and the fix to bug 171079, I have a handler with <activeWhen> and <enabledWhen> clauses that is not enabling when it should.

The handler should be enabled when the active part is NOT the snippet editor, and there is an available execution context (for a debugger evaluation). The contribution looks like the following:

<extension
       point="org.eclipse.ui.handlers">
    <handler
          class="org.eclipse.jdt.internal.debug.ui.evaluation.ForceReturnHandler"
          commandId="org.eclipse.jdt.debug.ui.commands.ForceReturn">
       <activeWhen>
 		  <with
                variable="activePartId">
                <not>
                <equals
                      value="org.eclipse.jdt.debug.ui.SnippetEditor">
                </equals>
                </not>
          </with>
       </activeWhen>
       <enabledWhen>
          <with
                variable="activeContexts">
             <test
                   property="org.eclipse.jdt.debug.ui.contains"
                   value="org.eclipse.jdt.debug.ui.evaluation">
             </test>
          </with>       
       </enabledWhen>
    </handler>
 </extension>

NOTES:
- when I remove the <not> clause for the SnippetEditor, and exchange it for an "equals specific part" clause, the active/enabled states work as expected. It seems that as soon as I insert the "not", the handler is never considered to be active.
- If I swap <active/enabledWhen> states (i.e. active when there is a context, and enabled when not in the snippet editor), it works (but that's not the behavior I want, since I want a different handler for the snippet editor).

I can attach a patch of the work in progress if needed.