Bug 250136 [KeyBindings] Conflicts should be accessible through API
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
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/BindingManager.java
}
		return activeBindingsByParameterizedCommand;
	}
	/**
	 * <p>
	 * Computes the bindings for the current state of the application, but
	 * disregarding the current contexts. This can be useful when trying to
	 * display all the possible bindings.
	 * </p>
	 * <p>
	 * This method completes in <code>O(n)</code>, where <code>n</code> is
	 * the number of bindings.
	 * </p>
	 * 
	 * @return A map of trigger (<code>TriggerSequence</code>) to bindings (
	 *         <code>Collection</code> containing <code>Binding</code>).
	 *         This map may be empty, but it is never <code>null</code>.
	 */
	public final Map getActiveBindingsDisregardingContext() {
		if (bindings == null) {
			
			return Collections.EMPTY_MAP;
		}
		
		final CachedBindingSet bindingCache = new CachedBindingSet(null,
				locales, platforms, activeSchemeIds);
		/*
		 * Check if the cached binding set already exists. If so, simply set the
		 * active bindings and return.
		 */