It's internal right now, but you can provide your own implementation of org.eclipse.e4.ui.internal.workbench.swt.IEventLoopAdvisor to the application context. You should be able to set this instance from the @PostContextCreate life cycle annotation.
Eclipse Platform committer. Ask me about Eclipse support, training, and consulting.
Hi - we've tried using this IEventLoopAdvisor mechanism and even with no processing inside the methods it results in very high CPU usage so doesn't appear to be practically usable (in Eclipse 4.4.1 on Windows Server 2008).
Does anyone know if this has been addressed since 4.4.1 ?