Bug 4597 – CLI favorites notifications

Bug 4597 - CLI favorites notifications

Summary:

CLI favorites notifications

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	CLI
Version:	6.5b3
Platform:	PC All

Importance:	P2 enhancement (vote)
Target Milestone:	---
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-12-14 08:04 UTC by Dr Lovegrove
Modified:	2008-12-18 11:12 UTC (History)
CC List:	2 users (show)

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 Dr Lovegrove 2006-12-14 08:04:37 UTC

When adding/removing/moving favorites, it would be useful if the CLI notified all listening clients.

Comment 1 Chris Owens 2007-02-12 14:55:33 UTC

cc'ing Fred for any comments he may have

Comment 2 Adrian Smith 2007-02-12 15:29:34 UTC

I'm looking at a new version of favorites for 7.0 - do you actually support the cli move command?  I was hoping to drop this in favor of just add and delete.  Favorites will be hiearchical so the index will become like xmlbrowser (well its based on mypicks)

As for a favorites changed, would a notify everytime it has potentialy changed do (when I save the underlying file)?

Comment 3 Fred 2007-05-19 14:12:52 UTC

Yes, I think a notif for every change would be good.

Also, I noticed the CLI doc has not been updated for the new commands. Triode, if you have a minute, that'd be great!

Comment 4 Fred 2007-05-19 14:13:22 UTC

CC'ing Triode...

Comment 5 Adrian Smith 2007-05-25 15:10:52 UTC

notification added for 7.0 in change 12133.

Comment 6 KDF 2007-05-25 18:42:19 UTC

please reopen if there are any issues.

Comment 7 Chris Owens 2008-03-07 09:04:00 UTC

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.