>* I agree with you, disabled should be the default. And as of last >Thursday and change 23928, that is the case. >http://svn.slimdevices.com/?view=rev&revision=23928 > Are you sure? I keep up to date with SVN, updating pretty much each day. I've updated since thursday, and my players seemed to be in Playmode=Off state. Maybe because I have run an intermediate version, the default didn't change from off to disabled?
>* the strange behavior you describe with the add button after entering >playlist or party mode is not at all the intended behavior. Sounds like >a bug. FWIW, I have not seen that behavior on my own system. Playlist >mode and party mode change the behavior of the play button, not the add >button. > The wiki seems to suggest that pressing the Add button when browsing the music library causes the mode to change to Playmode=Party. Add.hold seems to cancel Party mode. I don't see why these hotkeys are there at all. An option in settings to change mode is enough. If a user really needs a shortcut to change mode, they could add a hotkey via a custom map file. >The most important thing, IMO, is being able to put your >player in a state where the play button is not destructive to your >current playlist. I've never believed that part of our UI was done >correctly, and this is a way to get around that. > The most important thing is to not break existing pre-Sc7.3 functionality, which for me is perfect. If I hit play on an album, I expect it to play. If I want to add it to the current playlist, I hit the add button. It's the way almost all software media players I've ever used have worked, and seems perfectly sensible to me. An extra option (or plugin) that changes this functionality to be like walking into a bar in the 90's with a Jukebox in the corner may be what some people want, and I don't mind that, but it's not logical and should at least be disabled by default. >but it covers the most basic problem of handing your controller or >remote to someone at a party--hitting the play button destroying your >playlist. > Well, for me it's a non-problem being half solved. As long as "disabled" has no side-effects for existing functionality, I'm mainly happy (although there's more code being loaded that I'll never need, so a plugin that can be disabled/deleted would be better). Phil _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
