| [Display].timerExec() not executed when expected (as RCP does) [message #546397] |
Mon, 12 July 2010 15:59  |
 Bogdan B.
Messages: 50
Registered: July 2009 |
Member |
|
|
In my TreeViewer I add the following:
addPostSelectionChangedListener(new ISelectionChangedListener() {
public void selectionChanged(final SelectionChangedEvent e) {
System.out.println("schedule");
Display display = Display.getDefault();
display.timerExec(500, new Runnable() {
public void run() {
System.out.println("run");
}
}
}
});
The problem is that if I change the selection (SWT.FULL_SELECTION) I get to see "schedule", but "run" doesn't show up after 500ms. But if I click somewhere in the GUI (no matter where), then it actually runs, as if it would have waited for that click event.
In the RCP version of my app I get to see "run" like expected after 500ms, without needing to fire an extra event.
Does anyone know why this happens and how I could make it run like in RCP?
[Updated on: Mon, 12 July 2010 16:37] Report message to a moderator |
|
|
| Re: [Display].timerExec() not executed when expected (as RCP does) [message #546432 is a reply to message #546397] |
Mon, 12 July 2010 17:49  |
Ivan Furnadjiev
Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi Bogdan,
I'm not sure if this is related or not, but currently Tree (TreeViewer)
does not support SWT.FULL_SELECTION style flag (see bug 206780).
Best,
Ivan
On 07/12/2010 6:59 PM, Bogdan B. wrote:
> In my TreeViewer I add the following:
> addPostSelectionChangedListener(new ISelectionChangedListener() {
> public void selectionChanged(final SelectionChangedEvent e) {
> System.out.println("schedule");
> Display display = Display.getDefault();
> display.timerExec(500, new Runnable() {
> public void run() {
> System.out.println("run");
> }
> }
> }
> });
>
> The problem is that if I change the selection (SWT.FULL_SELECTION) I
> get to see "schedule", but "run" doesn't show up after 500ms. But if I
> click somewhere else, as if it would wait for some kind of event, then
> it actually runs.
>
> In the RCP version of my app I get to see "run" like expected after
> 500ms.
>
> Does anyone know why this happens and how I could make it run like in
> RCP?
|
|
|
|
|
| Re: [Display].timerExec() not executed when expected (as RCP does) [message #546931 is a reply to message #546666] |
Wed, 14 July 2010 16:13 |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
With "update the UI" I meant that the runnable that is passed into
timerExec is executed (as you usually want to run UI code within the
runnables).
timerExec (same accounts for asyncExec) do *not* block. Both methods
schedule the runnable for execution "at the next reasonable
opportunity". And here RAP behaves just like SWT, the runnables are
executed by readAndDispatch().
As you observed, the runnable gets executed with the next click. But if
you want it being executed more reliably and not just when someone
"accidentally" triggers a reuqest, you will have to activate the
UICallback. When it is active and timerExec() is called, it causes the
client to issue a request. The request in turn will call
readAndDispatch() which in turn will execute the runnables from
timerExec and asyncExec.
HTH
Rüdiger
On 13.07.2010 19:13, Bogdan B. wrote:
> Rüdiger Herrmann wrote on Mon, 12 July 2010 14:21
>> for (a)syncExec() and timerExec() to update the UI you will need to
>> activate the UICallback. See the FAQ for more details:
>> http://wiki.eclipse.org/RAP/FAQ#How_to_update_the_UI_from_a_
>> background_thread
>
> Thank you, Rüdiger, it works now (I'm not sure why though :))! I just
> changed my code as follows:
> addPostSelectionChangedListener(new ISelectionChangedListener() {
> public void selectionChanged(final SelectionChangedEvent e) {
> System.out.println("schedule");
> Display display = Display.getDefault();
> final String callbackId = new Date().getTime() + "_" + Math.random();
> UICallBack.activate(callbackId);
> display.timerExec(500, new Runnable() {
> public void run() {
> try {
> System.out.println("run");
> } finally {
> UICallBack.deactivate(callbackId);
> }
> }
> }
> }
> });
> What I still don't understand is why you said I needed to "update the
> UI". Since "run" was not printed out, it seems to me that the execution
> blocked when it met the display.timerExec() call. It didn't execute at
> all until it received my click event.
|
|
|
Powered by
FUDForum. Page generated in 0.02994 seconds
] 
Search
Help
Register
Login
Home
)! I just changed my code as follows: