View source

From Eclipsepedia

for FAQ Why do I get an invalid thread access exception?

You do not have permission to do that, for the following reason:

The action you have requested is limited to users in the group user.

You can view and copy the source of this page:

On most operating systems, drawing to the screen is an operation that needs to be synchronized with other draw requests to prevent chaos. A simple OS solution for this resource-contention  problem is to allow drawing operationsto occur only in a special thread. Rather than drawing at will, an application sends in a request to the OS for a redraw, and the OS will, at a time it deems appropriate, call back the application. An SWT 
application behaves in the same way. 

When the  end user of your application activates a menu or clicks a button, the OS will notify SWT, which in turn will call anyone listening to that button, until eventually the call chain ends with you. All these calls are made in  the same event loop thread.  Normally, a UI does not act on its own but reacts to stimuli from others. In general,  GUI applications are passive.

Therefore, when an application decides that it needs to live a life on its own, one option is for it to create another Java thread. A typical sample is the following:
<pre>
   new Thread(new Runnable() {
      public void run() {
         while (true) {
            try { Thread.sleep(1000); } catch (Exception e) { }
            Display.getDefault().asyncExec(new Runnable() {
               public void run() {
                  ... do any work that updates the screen ...
               }
            }
         }
      }
   }).start();
</pre>
This starts a timer that goes off every second and does some work.  Because the work will be done in an unsafe thread, we need to  request that SWT performs the task in a safe manner. We do this by  requesting that the default SWT display runs our runnable when it can using <tt>asyncExec</tt>. In practice, this request is served  as soon as possible.  Execution is performed asynchronously. In other  words, the request is placed in a queue with all other  <tt>asyncExec</tt> requests and dealt with in a first-come first-served manner.

The call to <tt>Display.asyncExec</tt> returns immediately, before the  drawing takes place. If you need to be guaranteed that the changes to the display took place before continuing, use <tt>Display.syncExec</tt>, which will suspend execution of the calling thread until the operation has finished.

Just about any SWT method that accesses or changes a widget must be called in the UI thread.  If you are unsure, check the method javadoc.  Any method that must be called in the UI thread will declare that it throws <tt>SWTException</tt> with value <tt>ERROR_THREAD_INVALID_ACCESS</tt>.

Avoid long-running processes in the UI thread as they will  make the UI unresponsive.  Do work that does not require UI  access in a separate thread, and use the <tt>asyncExec</tt> call only for UI updates.

== See Also: ==
*[[FAQ Does the platform have support for concurrency?]]
*[[FAQ Can I make a job run in the UI thread?]]

{{Template:FAQ_Tagline}}

Templates used on this page:

Template:FAQ Tagline

Return to FAQ Why do I get an invalid thread access exception?.

Retrieved from "http://wiki.eclipse.org/FAQ_Why_do_I_get_an_invalid_thread_access_exception%3F"