Community
Participate
Working Groups
See org.eclipse.jface.bindings.BindingManager.setActiveBindings(Map, Map, Map, Map) We currently use org.eclipse.jface.internal.InternalPolicy.currentConflicts to transport the conflicts around, it should be available through the BindingManager (and probably the IBindingService API) PW
Created attachment 116039 [details] Patch v01 Paul, Review and let me know whether I'm in the right direction.
(In reply to comment #1) > Created an attachment (id=116039) [details] > Patch v01 This looks like it's heading in the correct direction. As discussed, we should probably make the IBindingService method getConflictsFor(TriggerSequence) (and for now we just won't return the entire map of current conflicts). At the BindingManager level it's probably OK to return the entire map of current conflicts. PW
Created attachment 117042 [details] Patch v02 Patch with the required method & test added
I've released patch v02 with 2 minor changes: 1) turn javadoc references from KeySequence/KeyBinding to TriggerSequence/Binding 2) remove the BindingService#getCurrentConflicts() for now, since it wasn't used API Thanx, Prakash. PW
in I20081209-0100 PW