Best practice for passing values from a non-UI thread to a UI thread in an Eclipse plugin application

Question

Is there a best practice/shining example out there of passing values from a non-UI thread to a UI thread in an Eclipse plugin application?

Answer 1

You could use Display.asyncExec()

To allow background threads to perform operations on objects belonging to the UI-thread, the methods syncExec(Runnable runnable) and asyncExec(Runnable runnable) of Display are used.
These are the only methods in SWT that can be called from any thread.
They allow a runnable to be executed by the UI-thread, - either synchronously, causing the background thread to wait for the runnable to finish, - or asynchronously allowing the background thread to continue execution without waiting for the result.

A runnable that is executed using syncExec() most closely matches the equivalent direct call to the UI operation because a Java method call always waits for the result before proceeding, just like syncExec().

As illustrated by this thread:

I thought all those runnables or threads I give to Display.sync or asyncExec are 'Threads' and they get scheduled by the jvm or something along with the UI thread!
I never knew they are not considered the threads, but only pieces of code executed asynchronously by the UI thread!

This piece of code asynchronously executed by the UI thread might be a good place to access values (synchronized access) from other thread.

See "How to update a GUI from another thread in Java" as a practical example of passing a value to the UI thread.

(Note: the non-eclipse non-SWT way would have been, in Swing, by using a Swing Worker, as I mentioned a year ago)