Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343366 - Make Display#getDefault() work with threadless life cycle
Summary: Make Display#getDefault() work with threadless life cycle
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.4 M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 341763
  Show dependency tree
 
Reported: 2011-04-20 07:08 EDT by Rüdiger Herrmann CLA
Modified: 2011-05-04 07:25 EDT (History)
0 users

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-04-20 07:08:36 EDT 
Display#getDefault() currently accesses the UIThreadHolder from the RWTLifeCycle which is not present when RWT was configured to run with the threadless life cycle.
Display#getDefault() needs to be determined in a life cycle specific way.
Comment 1 Rüdiger Herrmann CLA 2011-05-04 07:25:51 EDT 
Introduced LifeCycleUtil#setUIThread() and #getUIThread(). The LifeCycle implementations use #setUIThread() to store/clear the current ui thread. Display#getDefault() now asks LifeCycleUtil to find out which thread (if any) is the UI thread for the current session.
Changes are in CVS HEAD.