Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363759 - Provide UICallBack#deactivate(Display,String)
Summary: Provide UICallBack#deactivate(Display,String)
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: 2.0 M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 392976
Blocks:
  Show dependency tree
 
Reported: 2011-11-14 17:01 EST by Rüdiger Herrmann CLA
Modified: 2012-12-17 14:42 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-11-14 17:01:49 EST
An active UI callback is usually deactivated from a background thread. This leads to code like this:
UICallBack.runNonUIThreadWithFakeContext( display, new Runnable() {
  public void run() {
    UICallBack.deactivate( "foo" );
  }
} );
I suggest to provide a new method UICallBack#activate( Display, String ) to avoid the above code. The new method would run UICallBack.deactivate( String ) in the context of the given display.
Comment 1 Ralf Sternberg CLA 2012-11-02 11:24:38 EDT
This will probably become obsolete with fixing bug 392976.
Comment 2 Ralf Sternberg CLA 2012-12-17 14:42:05 EST
The new ServerPushContext can be stopped from a background thread (see bug 392976).