Bugzilla – Full Text Bug Listing
| Summary: | Provide UICallBack#deactivate(Display,String) | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Rüdiger Herrmann <ruediger.herrmann> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 2.0 M4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 392976 | ||
| Bug Blocks: | |||
This will probably become obsolete with fixing bug 392976. The new ServerPushContext can be stopped from a background thread (see bug 392976). |
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.