Community
Participate
Working Groups
It appears to have been a problem since at least RC1. It works in my original workspace but not if I spawn a new one. It is broken in the inner also.
AbstractInformationControl's getInvokingCommandKeySequences() is returning 'null' for some reasons. JDT cannot do a keybinding comparison (to determine whether it is a request to show inherited members) so the second Ctrl+O becomes a no-op.
It seems we are never updating the ContextManager's active contexts. That seems to only ever be called when you request the active context ids from the EContextService. Paul, are we not calling this method often enough or are we supposed to be updating the manager when contexts are activated/deactivated?
Does this mean we're asking the wrong guy for an active binding? We're still depending on the legacy BindingService (strange that it used to work at all)? PW
We have fixed this problem by altering the way CommandLegacyWrapper tries to query for its keybinding.