Bug 218673 [DataBinding] SWTUtil should use timerExec(0,...) rather than asyncExec
In the event that you have a lot of cross-realm bindings, the current implementation of DisplayRealm generates a lot of flicker due to excess asyncExecs. It should be using SWTUtil.greedyExec instead. (Note: if you make this change, you may want to remove the display filter from WorkQueue. There are certain methods that do not like being called from an event filter, so running arbitrary asyncExecs during a filter may not always be safe.)
bundles/org.eclipse.jface.databinding/src/org/eclipse/jface/internal/databinding/provisional/swt/SWTUtil.java
*            target display
     * @param r
     *            runnable to execute
     */
    public static void cancelExec(Display d, Runnable r) {
        if (d.isDisposed()) {
            return;
        }
        WorkQueue queue = getQueueFor(d);
        queue.cancelExec(r);
    }
    /**
     * Returns the work queue for the given display. Creates a work queue if
     * none exists yet.
     * 
     * @param d
     *            display to return queue for
     * @return a work queue (never null)
     */
    private static WorkQueue getQueueFor(final Display d) {
        WorkQueue result;
        synchronized (mapDisplayOntoWorkQueue) {
            
            result = (WorkQueue) mapDisplayOntoWorkQueue.get(d);
            if (result == null) {
                
                result = new WorkQueue(d);
                final WorkQueue q = result;
                mapDisplayOntoWorkQueue.put(d, result);
                d.asyncExec(new Runnable() {