Bugzilla – Bug 8719
no window animation when pressing home in NowPlaying screensaver
Last modified: 2008-12-15 12:38:44 UTC
Found by Fletch and reported in forums. I've reproduced this as well: 2) If I press home from the NPSS, it goes home but does not use the usual "sliding window" animation (or whatever it's called). It just switches over to the home page.
fixed in r2696
Ben, I noticed that with this fix, there is still no animation if the SBC is on the home screen prior to the NPSS activating and I then press home. Is this expected?
hmmm..interesting (and fully reproduced). I'm not sure if the animation should be there, actually. What you are doing in essence in this special case is hitting the home key to view the underlying window, which is home. Should that have an animation? Not sure... fwiw, the reason there's no animation is that the Slimbrowser.goHome() method doesn't have any windows to hide (except for the screensaver window itself, which gets hidden without a transition, which IMO is correct behavior). -- goHome -- pushes the home window to the top function goHome() local windowStack = Framework.windowStack Framework:playSound("JUMP") while #windowStack > 1 do windowStack[#windowStack - 1]:hide() end end In the case of already being home, #windowStack == 1, therefore no window:hide() methods are called, thus no transition animation.
Yeah, I figured it was something like that which is why I asked if it was expected. Anyway, IMO it's not a big deal, but it is noticeably "different". I just wanted to make sure you were aware...
This bug has now been fixed in the 7.1 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.