Bugzilla – Bug 14067
Navigation into Now Playing should "bump" if current playlist is empty
Last modified: 2011-11-06 23:24:34 UTC
If the Current Playlist is empty, attempts to navigate into "Now Playing" should result in a "bump," rather than taking the user into an empty "Now Playing" state. examples: - pressing "home" button from the top item of the home menu - selecting the "Now Playing" menu option - pressing the "Now Playing" button on the fab4 remote (It will be unusual for the Current Playlist to be completely empty, so this case won't pop up very often, but it's still very nice-to-have).
Bad idea. Bumping when it isn't obvious why you're bumping is going to be construed as "broken" or "stuck". There's already a lot of unexplained bumping when there are connection issues, so it will also make troubleshooting more difficult. What do you mean an empty playlist will be unusual? Depends on your usage pattern, I suppose. I commonly clear the playlist. What's the harm in displaying an empty Now Playing screen? In NP I can see (and on Fab4, I can *adjust*) the volume level, the repeat state, and the shuffle state even when the playlist is empty. Example: I walk up to the Fab4 and wish to play something, but I have no idea what the volume level is. How do I figure that out _before_ I blast something through the speakers at 3AM?
I would not make this a P1 at this late date.
To quote Matt Weldon: > Yeah Caleb, if any button (other than power of course) should ALWAYS work, it > should be the volume knob, hopefully for obvious reasons... https://bugs-archive.lyrion.org/show_bug.cgi?id=13053#c7 But that won't be possible in the Fab4 touch ui if you can't get to the NP screen, will it?
(In reply to comment #3) > To quote Matt Weldon: > > > Yeah Caleb, if any button (other than power of course) should ALWAYS work, it > > should be the volume knob, hopefully for obvious reasons... > > https://bugs-archive.lyrion.org/show_bug.cgi?id=13053#c7 > > But that won't be possible in the Fab4 touch ui if you can't get to the NP > screen, will it? Hehe you're taking me a bit out-of-context. That was a discussion of hardware buttons. And the fab4 ships with a remote that has an always-functional volume control. Also, by definition, if the playlist is empty, music won't be playing. ;-) I would only want this behavior to exist, in fact, if no music was playing.
Create a touch interface where you can only do some things with the remote. Makes a lot of sense. The on-screen touch controls are the functional equivalent of the hardware controls on the Radio. You could have designed a dedicated volume control onto the face of the device, but chose to do everything in software. But now you want to block access to those controls for... some reason. You would want to turn the volume down, or at least verify the volume level, _BEFORE_ playing something. It's also important to be able to set Shuffle _BEFORE_ queuing up a playlist or album, otherwise you always get track #1 of the playlist first.
(In reply to comment #5) > Create a touch interface where you can only do some things with the remote. > Makes a lot of sense. The on-screen touch controls are the functional > equivalent of the hardware controls on the Radio. You could have designed a > dedicated volume control onto the face of the device, but chose to do > everything in software. But now you want to block access to those controls > for... some reason. > I made zero hardware decisions for fab4, FWIW, other than getting a dedicated "Now Playing" button added to the remote. If it had been up to me, there would be some dedicated hardware buttons on the device. It is what it is. > You would want to turn the volume down, or at least verify the volume level, > _BEFORE_ playing something. Which is why you have a remote with volume controls. (Also, you don't have to _SHOUT_ ;-). It's also important to be able to set Shuffle > _BEFORE_ queuing up a playlist or album, otherwise you always get track #1 of > the playlist first. Again, I'm not claiming it's ideal, but even as it is today it's much more convenient to use the remote in the case you described. ---------- So basically your counter-proposal is to leave it the way it is? Have a blank Now Playing screen? Just so you can touch the Now Playing button, then press down again to adjust the volume, before starting to play something, insteead of using the remote? You don't think that's going to feel the slightest bit awkward?
Run out of time for 7.4
Tom, the original bug request stands. Please retarget as appropriate and fix when you can.
7.4.x milestone is in the past
Tom is no longer available to us
Unassigned bugs cannot have a priority.