To elaborate, it's as Peke and Lowlander explained: if the sort order is changed but not saved:Could you please explain what possible useful purpose it serves?
1) then the only indication that the Playlist order is not in its sort order is that the entries in the # are out of order. this is important to know because otherwise:
- it's unclear that the track order displayed isn't the actual order of tracks in the playlists
- it explains why tracks can't be dragged/dropped to change order of a static playlist
2) it provides an obvious way to revert the display order to the playlist order--by sorting by the # column (there are alternatives such as using F5 or exiting/re-entering the node, but most users aren't aware of this)
That said, we'll look into what can be done, though it may not make it into the initial release.
-Rusty