Warning, /sdk/kcachegrind/libcore/BUGS is written in an unsupported language. File is not indexed.
0001 Visualization state problem (16.12.08) 0002 -------------------------------------- 0003 0004 A view on profile data should use its own visualization state, such 0005 as currently selected/activated item, attributes such as 0006 absolute/percentage and so on. 0007 A view can be console output, a toplevel window (we want to support 0008 multiple for the same data!), or even subviews inside of a view 0009 (different cost item activations (REALLY NEEDED)). 0010 0011 Currently, this visualization state is stored either 0012 * in the single Configuration object 0013 * attribute of toplevel windows (eg. options from tool bar) 0014 0015 Problems: 0016 * Which configuration options persistent between runs of the app? 0017 0018 Todo: 0019 * Use separate VisualizationState objects