Bug 1543 – pressing/holding play on Now Playing to save playlist gives an error

Bug 1543 - pressing/holding play on Now Playing to save playlist gives an error

Summary:

pressing/holding play on Now Playing to save playlist gives an error

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	SlimService
Version:	unspecified
Platform:	All All

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Dave Cohen

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-05-16 13:05 UTC by Kevin Pearsall
Modified:	2009-09-08 09:25 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 Kevin Pearsall 2005-05-16 13:05:37 UTC

says:

PROBLEM: NO SAVED PLAYLIST FOLDER.
Visit Server Settings to fix this.

Comment 1 Dave Cohen 2005-05-16 16:29:08 UTC

removed SavePlaylist plugin.

Comment 2 Kevin Pearsall 2005-05-18 10:59:08 UTC

how do you add something to favorites using the remote then?

Comment 3 Kevin Pearsall 2005-05-18 10:59:45 UTC

oh.  press and hold add.  but that's very different from the behavior in
slimserver, where pressing/holding add adds it to your zapped songs playlist...

Comment 4 Dave Cohen 2005-05-18 11:37:52 UTC

Probably the best way is...

When viewing a playable thing, press right for more information.  The last item
in the list will be "press right to add to favorites"  (or, if its already a
favorite, press right to delete).

I'm open to other options including pressing and holding play.  I'm CCing Dean
as he usually has opinions on these matters.

Comment 5 Kevin Pearsall 2005-05-18 11:45:00 UTC

well i think it would be nice to keep the press/hold play consistent with the
server at least...

Comment 6 Blackketter Dean 2005-05-18 13:24:49 UTC

Agreed, I'm planning a UI review to sync up the server and the service in this regard.  Stay tuned.

Comment 7 James Richardson 2008-12-15 12:13:34 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.