Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 396744

Summary:

timerExec(-1, runnable) behaves differently between RWT and pure SWT

Product:

[RT] RAP

Reporter:

Eiro Neemous <dr.neemous>

Component:

RWT

Assignee:

Project Inbox <rap-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

2.0

Target Milestone:

2.0 RC1

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
examples	none

Description Eiro Neemous

2012-12-17 07:57:09 EST

timerExec(-1, runnable) can cancel timertask in pure SWT, but in RWT it can't.
Attached zip includes 3 java classes, you can test them to check :)

Comment 1 Eiro Neemous

2012-12-17 07:58:00 EST

Created attachment 224798 [details]
examples

Comment 2 Ralf Sternberg

2012-12-19 16:52:09 EST

Cancelled runnables haven't been removed due to a typo in TimerExecTask#removeTask(Runnable). Moreover, multiple calls to timerExec with the same runnable resulted in multiple tasks instead of re-scheduling the existing task.
Fixed with commit 1048ad9e8d9243ab14070943499ea901eaad0c95.