Bug 7820 – Play doesn't cancel fast forward mode from controller

Bug 7820 - Play doesn't cancel fast forward mode from controller

Summary:

Play doesn't cancel fast forward mode from controller

Status:	CLOSED FIXED

Product:	SB Controller
Classification:	Unclassified
Component:	SB Server
Version:	unspecified
Platform:	PC Debian Linux

Importance:	-- normal (vote)
Target Milestone:	7.1
Assigned To:	Alan Young

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-04-14 13:29 UTC by Marc Auslander
Modified:	2008-12-15 12:38 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marc Auslander 2008-04-14 13:29:54 UTC

Hold fwd until fast forward mode is engaged.  Pressing play does not cancel fast forward.  The only way I've found to cancel fast forward is to press pause twice.

Comment 1 Marc Auslander 2008-04-14 13:33:48 UTC

sorry - forgot to say that squeezecenter is 7.1 - 18719  and controller software is 7.1 r2224

Comment 2 Chris Owens 2008-04-16 09:11:09 UTC

Alan notes this isn't complete yet.

Comment 3 Alan Young 2008-04-16 09:58:48 UTC


*** This bug has been marked as a duplicate of bug 7068 ***

Comment 4 Alan Young 2008-06-04 07:27:28 UTC

Fast-forward now replaced by Song Scanner functionality.

Comment 5 James Richardson 2008-07-10 15:32:07 UTC

Verified fixed in 7.1-21630

Comment 6 Chris Owens 2008-07-30 15:28:18 UTC

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.

Comment 7 James Richardson 2008-12-15 12:38:24 UTC

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.