Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364863 - [Display] timerExec() should activate and deactivate UICallback by itself
Summary: [Display] timerExec() should activate and deactivate UICallback by itself
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-25 13:09 EST by Rüdiger Herrmann CLA
Modified: 2011-11-25 17:22 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.