| bg-job/ui-thread problem [message #109684] |
Fri, 17 October 2008 12:46  |
Eclipse User |
|
|
|
Originally posted by: erdal.karaca.airbus.com
A local copy of the Display (as Display.getDefault() does not work
properly) is used in a background job to execute code using
Display.syncExec(...) in the ui thread. Unfortunately, this yields a
deadlock (hint: UICallBackManager.addSync(...))...
Using Display.asyncExec() seems to work, but this is not wanted...
|
|
|
| Re: bg-job/ui-thread problem [message #109861 is a reply to message #109684] |
Mon, 20 October 2008 08:11  |
| Eclipse User |
|
|
|
Originally posted by: rherrmann.innoopract.com
Erdal,
thanks for the hint. If you can make it reproducible with a
self-contained code snippet please file a bug.
Cheers,
Rüdiger
Erdal Karaca wrote:
> A local copy of the Display (as Display.getDefault() does not work
> properly) is used in a background job to execute code using
> Display.syncExec(...) in the ui thread. Unfortunately, this yields a
> deadlock (hint: UICallBackManager.addSync(...))...
> Using Display.asyncExec() seems to work, but this is not wanted...
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03766 seconds
] 
Search
Help
Register
Login
Home
