1 TODO for the next engine framework:
3 * emit stateChanged() with no parameter and force controller to read the state from
4 EngineBase::state() instead, as this makes things more likely to be consistent
5 * combine load() and play() as it just complicates things for engine development (eg
6 crossfade is a bitch for me due to the separation
7 * setVolumeSW( double ), to give more resolution for setting volume
8 * Make EngineObserver system use engineStateChanged( oldState, newState )
9 * Don't do above function for Play on every track? Is this ever useful?
10 * Would be useful if engineNewMetaData and stateChanged for Play weren't separate?
11 * setVolumeSW uses a log function, volume() doesn't so you get different values back to
12 what you expect. Really we should provide a volumeToLog( int ) function for engines to
13 use internally as some engines may already apply a log function anyway.