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

Bug 364863

Summary: [Display] timerExec() should activate and deactivate UICallback by itself
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: ivan, rsternberg
Version: unspecified   
Target Milestone: 1.5 M4   
Hardware: All   
OS: All   
Whiteboard:

Description Rüdiger Herrmann CLA 2011-11-25 13:09:07 EST 
Currently Display#timerExec() only actually works if the application programmer activates the UICallback before calling this method. In SWT, timerExec() works without further assistance.

I suggest that timerExec() internally activates and deactivates the UICallback as is necessary to fulfill its function. As timerExec() can only be called from the UI thread, it is safe to activate the UICallback from within timerExec().
Comment 1 Rüdiger Herrmann CLA 2011-11-25 17:22:39 EST 
timerExec() now activates and deactivates the UICallback by itself. Changes are in CVS HEAD.