Bug 5534 – Slimtray icon: needs additional option for "Never auto-start"

Bug 5534 - Slimtray icon: needs additional option for "Never auto-start"

Summary:

Slimtray icon: needs additional option for "Never auto-start"

Status:	CLOSED INVALID

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Slimtray
Version:	7.0
Platform:	PC All

Importance:	P2 enhancement (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-09-21 13:12 UTC by Dan Evans
Modified:	2008-12-18 11:12 UTC (History)
CC List:	1 user (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 Dan Evans 2007-09-21 13:12:45 UTC

There is some confusion on how the Slimtray icon displays its options.  

There are checkmarks next to the options for "Auto run at system start" and "Auto run at login" but nothing to indicate how to never auto-run SlimServer.  (I know that by having no option checked that achieves that setting, but we could be clearer.)

Suggestion: add an additional checkable option labeled, "Never automatically run"

Comment 1 Spies Steven 2007-09-21 13:21:08 UTC

Just for reference the SlimServer Preference Pane for Mac OS X shows the following as a drop down menu:

Automatically start:
Never
When I log in
When system boots

Perhaps we can adopt the same wording for Slimtray but use checkmarks instead.

Comment 2 Michael Herger 2007-11-07 07:03:54 UTC

This bug is kind of obsolete:
- in application mode you can enable or disable auto start - there's only this one single option
- in service mode you can't manage this behaviour from SqueezeTray

Comment 3 Chris Owens 2008-03-07 09:04:55 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.