Debian Codegraph @

libcore/BUGS

raw
1 Visualization state problem (16.12.08)
2 --------------------------------------
3
4 A view on profile data should use its own visualization state, such
5 as currently selected/activated item, attributes such as
6 absolute/percentage and so on.
7 A view can be console output, a toplevel window (we want to support
8 multiple for the same data!), or even subviews inside of a view
9 (different cost item activations (REALLY NEEDED)).
10
11 Currently, this visualization state is stored either
12 * in the single Configuration object
13 * attribute of toplevel windows (eg. options from tool bar)
14
15 Problems:
16 * Which configuration options persistent between runs of the app?
17
18 Todo:
19 * Use separate VisualizationState objects