Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » Runnable asynExec

Show: Today's Messages :: Show Polls :: Message Navigator

Runnable asynExec [message #461569]

Fri, 12 January 2007 15:22

Marc

Messages: 9
Registered: July 2009

Junior Member

Is there beside the busyIndicator any difference in the way these
runnables are executed in a RCP application ?

getSite().getShell().getDisplay().asyncExec(new Runnable() {
public void run() {
treeViewer.refresh();
}
});

BusyIndicator.showWhile(Display.getCurrent(), new Runnable() {
public void run() {
treeViewer.refresh();
}
});

Report message to a moderator

Re: Runnable asynExec [message #461571 is a reply to message #461569]

Fri, 12 January 2007 15:47

Carsten Spieker

Messages: 197
Registered: July 2009

Senior Member

Hi,

usually you use the asyncExec in this context

PlatformUI.getWorkbench().getDisplay.asyncExec(*);

in order to execute some code in the UI Thread.
Maybe you read some data or so in another thread and you want to update some
GUI elements,
then you have to use the asyncExec(*) or the syncExec(*) to get access to
the main UI thread, as far as I know.

Greetz,
Carsten

"pigna" <pijnmar@hotmail.com> schrieb im Newsbeitrag
news:598d1f7011e2020a69c29174d1b8cc83$1@www.eclipse.org...
> Is there beside the busyIndicator any difference in the way these
> runnables are executed in a RCP application ?
>
> getSite().getShell().getDisplay().asyncExec(new Runnable() {
> public void run() {
> treeViewer.refresh();
> }
> });
>
>
> BusyIndicator.showWhile(Display.getCurrent(), new Runnable() {
> public void run() {
> treeViewer.refresh(); }
> });

Report message to a moderator

Re: Runnable asynExec [message #461573 is a reply to message #461569]

Fri, 12 January 2007 17:31

Francis Upton IV

Messages: 472
Registered: July 2009
Location: Oakland, CA

Senior Member

Yes, a big difference:

pigna wrote:
> Is there beside the busyIndicator any difference in the way these
> runnables are executed in a RCP application ?
>

This one is executed asynchronously on the display thread. If you are
currently on the display thread, then the execution is deferred until
the main event loop is re-entered.

> getSite().getShell().getDisplay().asyncExec(new Runnable() {
> public void run() {
> treeViewer.refresh();
> }
> });
>
>

This is executed synchronously (it uses Display.syncExec(), meaning it
will run as if you had no wrapper.

> BusyIndicator.showWhile(Display.getCurrent(), new Runnable() {
> public void run() {
> treeViewer.refresh(); }
> });

Platform UI Committer for Common Navigator

http://wiki.eclipse.org/index.php/Common_Navigator_Framework
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/guide/cnf.htm

Report message to a moderator

Re: Runnable asynExec [message #461620 is a reply to message #461573]

Sat, 13 January 2007 21:30

Marc

Messages: 9
Registered: July 2009

Junior Member

Thank you both for your answers. Learning every day :-)

So if I'm correct if you a scenario where three viewers need simultaneous
update one should go for solution one. Or is there even a better way?

The asyncExec does not change cursor to wait as seconds example did. How
can I achieve same behaviour cursor wise?

Report message to a moderator

Previous Topic:	[Newbie] View notification
Next Topic:	removing annoying coolbar actionsets

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 00:48:28 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter