View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003083 | MMW v4 | Main Panel/Toolbars/Menus | public | 2007-06-01 19:29 | 2007-08-03 21:29 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | reopened | ||
| Product Version | 2.5.5 | ||||
| Fixed in Version | 3.0 | ||||
| Summary | 0003083: Party Mode: Change handling (settings) of audio controls enable status | ||||
| Description | If 'Disable removal and re-ordering of tracks in Now Playing' is enabled, the user can still drag and drop tracks into the middle of the Now Playing list (note: Play Now and Play Next are disabled--as expected). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1058 | ||||
|
|
D&D is disabled, however, for some reason, Play Now and Play Next aren't disabled and I thought that they were previously when this option is enabled. |
|
|
Yes, you are right 'Play Last' and 'Play Next' haven't been disabled in this case althoug they should be. 'Play Now' depends rather on 'Disable Player / Audio controls' setting. |
|
|
Tested 1041. I don't think it's quite right: At the moment, if re-ordering is disabled, then only 'Play Now' is active, which allows the user to start playing any track that they select at any point in the playlist. What I think is required is for 'Play Now' and 'Play Next' to be disabled (since both of those cause re-ordering of the playlist (i.e. allow requests to 'jump the queue'). The only function that should be enabled is 'Play last'. |
|
|
As pointed out by Ludek, If Disable Player / Audio controls --> play/pause is disabled And if Disable reordering --> Play Now, Play Next is disabled ==>there is a problem of how to start the player in Party mode if both of these are checked off. Solution: Users can start playback prior to switching to Party mode OR we can allow the Player's play button to work even if 'Disable Audio/Player' is enabled _just to start the player_ (once started, player controls would be completely disabled). |
|
|
Fixed in build 1042. There is _NOT_ the problem of how to start the player in Party mode if both of these are checked off, because this depends on how double-click action is set. By default it is set to 'PlayNow' when playback is stopped and to 'PlayLast' if playback is performed so after the first double-click it starts playing and then there is no such problem. |
|
|
There's still a small problem: If Reordering is disabled, user can still get a track inserted by: -stopping playback -selecting a track and double-clicking (this causes 'Play Now' play the currently selected track at the current position in Now Playing) To correct this we could do either of the following: a) disable 'stop' when re-ordering is disabled . 'Stop' inherently re-orders the playlist by causing a track to play more than once (e.g. a user who likes a track can press stop and then play to play it again from the beginning), and disabling this will prevent users from pressing stop in order to 'Play Now' new tracks. b) add a "'Play Now' Action:" of "Play jukebox style" (starts the player at the current position of Now Playing, or with the selected Track(s) in cases where the Now Playing list is empty). a) is probably the best solution since it's simpler, and fixes 2 issues. |
|
|
I would say that stop button rather depends on [x] Disable Player / Audio Controls configuration only. Causing a track to play more than once doesn't re-order the Now Playing list, isn't it? Selecting a track and double-clicking depends on how the double-click action is set (default is 'Play Last' when tracks are playing and this doesn't re-order Now Playing too). I think that current implementation is all right, because as I wrote these 2 options are in conflicted state and user rather disable these both (re-ordering and Player controls too). If Player controls are enabled there are other problems, if you click [>>] 'Next' button on the Player then 'Keep Only X tracks' functionality could delete some tracks from NP list. Therefore I think that in such a case user disables also Player controls. |
|
|
The scenarios that I see are: 1) Audio Controls Disabled / Reordering disabled (strict jukebox mode--untrusted users) 2) Audio Controls Enabled / Reordering enabled (party with trusted users) 3) Audio Controls Disabled / Re-ordering enabled (not very useful) 4) Audio Controls Enabled / Re-ordering disabled (useful for many parties where people will be adding to the playlists, but occasionally there'll be a need to Pause/Play/Adjust Volume) If I understand your point, you're saying that the most useful scenarios are 1) and 2) and the fact that 4) doesn't work perfectly well (because users can re-order tracks by stopping) isn't that much of an issue. I would disagree, though--I think the fourth scenario is probably very useful and that it should work correctly. If we agree that scenario 4) is useful, then the question is 'how do we prevent re-ordering/accidental re-ordering' in scenario 4). If we don't take the approach a), do you think the alternate approach b) would work? A third possibility c) would be to change the controls as follows--and this would eliminate all inconsistencies and provide a more useful experience I think: c) Change Disable Audio Controls: to disable Volume, Play, Pause d) Change Disabled Re-ordering: to include Stop/Forward/Back |
|
|
ok, if we see the scanario 4) as useful: The altrnated approach b) would not work too, because of the problem I have already mentioned in my last note (clicking the [>>] 'Next' button on the Player can trigger the 'Keep Only X tracks' functionality which can cause deleting of some tracks from NP). Therefore I suggest to join it: [] Disable Audio/Player Controls and re-ordering of NP --[] Enable Volume, Play, Pause The second checkbox would be enabled only if the first is enabled. |
|
|
Good idea. I'd reword it slightly: [ ] Disable Player controls and Track reordering [x] Enable volume, play/pause controls |
