| org.eclipse.ui.startup and threads [message #448560] |
Wed, 26 April 2006 08:55  |
Eclipse User |
|
|
|
Documentation on org.eclipse.ui.startup extension says:
Once the workbench is started, the method earlyStartup() will be called
from a separate thread.
If I have more than one startup class defined, it seems that they are all
started in the same thread, e.g. if one class is blocking (listening to
socket), other won't be started until the first one ends.
Am I right here?
It's not a problem to implement Runnable (or similar) but it is good to
know and the documentation is a little bit vague.
Thanks,
Davor
|
|
|
| Re: org.eclipse.ui.startup and threads [message #448592 is a reply to message #448560] |
Thu, 27 April 2006 08:53  |
| Eclipse User |
|
|
|
It's done from EarlyStartupRunnable in the org.eclipse.ui.workbench plugin.
You're right the document isn't very explicit. The message they wanted
to give was that your early startup code would not be called in the UI
thread, so if you want to update UI things you would need to take extra
steps.
They are run in a separate thread from the UI thread, but it's actually
a loop that just calls #earlyStartup() on each startup extension element
it can find.
Later,
PW
|
|
|
Powered by
FUDForum. Page generated in 0.05190 seconds
Home