Bugzilla – Bug 11117
touching pause on fab4 when on the now playing screen should reset the screensaver timer
Last modified: 2009-09-08 09:19:58 UTC
If you are playing music and in the NP screen (as a screensaver) touching the pause button will immediately kick in the clock screensaver. The screensaver should be reset.
Before making this change, I want to point out the other discussion related to this issue. See, for instance 10854 - https://bugs-archive.lyrion.org/show_bug.cgi?id=10854 When looking at that bug, I found that the "pause to stopped SS" design was an intentional design choice made for the controller some time ago. I recall someone (Ben perhaps) explaining the rationale for the behavior, but it eludes me now. Just wanted to be sure that you are aware of the history before changing this behavior.
from campfire Tom W. ben, when you get a chance, could you have a look at https://bugs-archive.lyrion.org/show_bug.cgi?id=11117 and comment if you can about the rationale for the current behavior. It's the "pause the NP SS into the stopped SS" issue begin raised in a new bug by Dean. Richard T. probably more a question for me. Tom W. oh, super Ben K. i think the behavior works well for the controller, but only because the pause button is always there on fab4, not so much Richard T. when the music stops it should switch to the stopped screensaver, that was how it is designed. Ben K. but pause, then unpause is a very common use case. answering a phone call, e.g. Richard T. i think the bug, more noticeable on fab4 but also a bug on the controller, is that if you stop the music yourself, then the screensaver timer should expire before switching screensavers. but i think we need to understand more about the now playing screen before trying to fix this. Ben K. i'd always thought that the immediate switch was by design Richard T. on jive it has two modes, 'screensaver' and 'normal'. no i don't think so. i expect that we'll only have one mode of screensaver in the future. so that bug may or may not need fixing after that change.
Ah, this is a dup. *** This bug has been marked as a duplicate of bug 10854 ***