1) <MarkerColor> is used as a fallback by all the WaveformRenderMark (hotcues) and WaveformRenderMarkRange (loops) on the waveform and overview. So if no <Color> is provided for a mark or markrange then it falls back on <MarkerColor> of the parent.
I think we should get rid of MarkerColor everywhere and make WaveformMark and WavformMarkRange both use <AxesColor> as the fallback if no <Color> is present.
2) m_qMarkerColor can now be removed from WOverview I believe.
3) Not sure I see the difference between AxesColor and PlayPosColor?
1) <MarkerColor> is used as a fallback by all the WaveformRenderMark (hotcues) and WaveformRenderM arkRange (loops) on the waveform and overview. So if no <Color> is provided for a mark or markrange then it falls back on <MarkerColor> of the parent.
I think we should get rid of MarkerColor everywhere and make WaveformMark and WavformMarkRange both use <AxesColor> as the fallback if no <Color> is present.
2) m_qMarkerColor can now be removed from WOverview I believe.
3) Not sure I see the difference between AxesColor and PlayPosColor?