Why having a single thread for display is so important? [message #536107] |
Thu, 27 May 2010 02:03  |
Eclipse User |
|
|
|
Having a single thread for display has forced me many times to build an application which is multi threaded...
And everybody knows about the problems of a multithreaded application.
So i was wondering is it worth it to have a single threaded display??
[Updated on: Thu, 27 May 2010 08:09] by Moderator
|
|
|
|
|
Re: Why having a single thread for display, so important? [message #536425 is a reply to message #536169] |
Fri, 28 May 2010 03:37  |
Eclipse User |
|
|
|
Okay, sorry for my invective.
If the background task only needs to update the UI, it could run the processing in the UI thread and call Display.update() regularly. But this might not be possible, if you are not able to call it at least every few seconds. Then you really need separate thread, but the communication can be simple, if the task is relatively independent.
Viliam
On 27. 5. 2010 12:14, vijay wrote:
>
> and since the heavy operation should be able to run in background,hence
> inevitable it becomes a multi threaded application...
> In fact an RCP application is a multithreaded application(pls dont tell
> me to go to RCP Forum :) )
> --
|
|
|
Powered by
FUDForum. Page generated in 0.05330 seconds