FS#10347 - First buttonpress/wheel movement after exiting PictureFlow unrecognized by player

Attached to Project: Rockbox
Opened by David Thacker (epithetless) - Thursday, 18 June 2009, 02:06 GMT
Last edited by Thomas Martitz (kugel.) - Friday, 19 June 2009, 21:21 GMT
Task Type Bugs
Category Plugins
Status Closed
Assigned To No-one
Operating System Sansa e200
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Quite often, when exiting PictureFlow using the Power button of my Sansa e280, the first subsequent buttonpress/scrollwheel movement goes unrecognized by the player.

Though it doesn't happen 100% of the time, I am able -- more often than not -- to reproduce this behavior by entering PictureFlow, opening an album, scrolling down, pressing the Play button (even though it's not mapped to anything and has no immediate effect), pressing the Power button to exit PictureFlow, and then attempting to press another button in the "Demos" screen. I typically have to press the button a second time for the desired action (e.g. backing out of the "Demos" menu or returning to the WPS) to take effect.

The same thing often occurs if -- rather than pressing Play -- I press the Right or Select button while inside an album list (thus playing the highlighted track), and then exit via the Power button.

Performing the above actions and then exiting via the "Quit" option in the PictureFlow Main Menu does not seem to produce this behavior.

I'm using build r21322 at the moment.
This task depends upon

Closed by  Thomas Martitz (kugel.)
Friday, 19 June 2009, 21:21 GMT
Reason for closing:  Duplicate
Additional comments about closing:  See  FS#10097 
Comment by Michael Chicoine (mc2739) - Thursday, 18 June 2009, 22:05 GMT
This sounds like it may be the same as  FS#10097  and according to Michael Sevakis (MikeS) it also occurs with other plugins.
Comment by David Thacker (epithetless) - Friday, 19 June 2009, 00:17 GMT
Yes, it does sound like the same bug. Thanks for the notification.