persistent interface state
to perform non-trivial work in an elaborate user interface it is crucial for elements to be able to retain their shape and state. The UI must be able to recall which elements where folded or expanded, which zoom levels where used, which view styles where selected on which parts and the like. We cannot implement such on a case by case base, we need a general support framework, otherwise it won't happen....
Change history
(7)
| blockedby: |
1043, 975 → 975, 1043
|
| blocking: |
979, 951 → 951, 979
|
| blockedby: |
975, 1043 → 975, 1043, 1065
|
| blockedby: |
975, 1043, 1065 → 975, 1043, 1065, 1144
|
| blockedby: |
975, 1043, 1065, 1144 → 975, 1043, 1065, 1144, 1157
|
| blockedby: |
975, 1043, 1065, 1144, 1157 → 975, 1043, 1065, 1144, 1157, 1194
|
| blockedby: |
975, 1043, 1065, 1144, 1157, 1194 → 975, 1043, 1065, 1144, 1157, 1194, 1398
|
| blockedby: |
975, 1043, 1065, 1144, 1157, 1194, 1398
|
| blocking: |
951, 979
|
| Parent Tickets: |
→ 951, 979
|
| Sub Tickets: |
→ 975, 1043, 1065, 1144, 1157, 1194, 1398
|
As a first step towards a solution, I've now installed a simple map-based state recording service into the prepared hook in UI-Bus /
CoreServiceMoreover, there is now a wiring between
UiStateand this recording service -- but obviously there needs to be done way more on this frontier...see
StateMapGroupingStorage_testBusTerm_test::replayStateMark()