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

Bug 576574

Summary: Display.timerExec RWT behaves very differently to pure SWT
Product: [RT] RAP Reporter: Vincent Lustermann <Vincent.Lustermann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: digga1404, mknauer, peter.hermsdorf
Version: unspecified   
Target Milestone: 3.19   
Hardware: All   
OS: All   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396744
https://git.eclipse.org/r/c/rap/org.eclipse.rap/+/186431
https://git.eclipse.org/c/rap/org.eclipse.rap.git/commit/?id=26fd6f8abab7db8f67743f13f7b02c8be4bd3f67
Whiteboard:
Attachments:
Description Flags
remove /**/ to switch between RWT and SWT none

Description Vincent Lustermann CLA 2021-10-12 08:30:53 EDT
Created attachment 287304 [details]
remove /**/ to switch between RWT and SWT

the pure SWT implementation of Dislay.timerExec collects subsequent calls with the very same runnable and only executes it only once.

The same code executed with an RAP implementation will throw an IllegalStateException with "Task already scheduled or cancelled"
Comment 1 Eclipse Genie CLA 2021-10-13 07:04:56 EDT
New Gerrit change created: https://git.eclipse.org/r/c/rap/org.eclipse.rap/+/186431
Comment 3 Vincent Lustermann CLA 2021-10-14 03:06:53 EDT
just tested with the fixed 3.19 jar - works fine!

thank you very much for your time and effort!
Comment 4 Markus Knauer CLA 2021-10-14 03:27:06 EDT
Thank you for the feedback. The fix is now part of our (delayed) 3.19 M1 milestone release from yesterday.