| Summary: | UIProcess should have change listener support | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Riena | Reporter: | Christian Campo <christian.campo> | ||||
| Component: | Look And Feel | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | nobody | ||||
| Version: | 4.0.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Christian Campo
Created attachment 203401 [details]
proof of concept but not code to be committed
This code was create by Heiko Barth and is not intended to be committed into CVS. It shows an idea on how to address the problem with the SubModuleController which lead to the discussion that the best solution is a IUIProcessChangeListener
Fixed and pushed
Usage:
UIProcess p = new UIProcess(...);
p..addUIProcessChangedListener(new IUIProcessChangeListener() {
public void onInitialUpdateUI(final int totalWork) { ... }
public void onFinalUpdateUI() { ... }
});
Reopening since a predictable execution order is desired. The IUIProcessChangeListeners should be called _after_ the UIProcess.initialUpdateUI() method. The IUIProcessChangeListener will be always called after the methods UIProcess.initialUpdateUI() and UIProcess.finalUpdateUI()
Usage:
UIProcess p = new UIProcess(...);
p..addUIProcessChangedListener(new IUIProcessChangeListener() {
public void afterInitialUpdateUI(final int totalWork) { ... }
public void afterFinalUpdateUI() { ... }
});
|