Open GoogleCodeExporter opened 9 years ago
I'll look in to adding this
Original comment by j...@gmail.com
on 3 Mar 2008 at 3:36
Hi,
The implemented solution (as of Secrets 1.0b18) is actually not working. The
Quit button is a very good idea
for all applications, but not for Front Row (and also Dashboard in fact).
Indeed, sending the quit apple event to Front Row simply does not work. To
verify:
1. Launch Front Row
2. Exit Front Row with the escape key (or the remote menu button)
3. Enable or disable HD trailers setting in Secrets
4. Click the Quit button in Secrets
5. In Terminal: $ps ux | grep "Front Row" ---> Front Row is still running!
It means that Front Row will not be aware of the new settings set by Secrets as
they are read at launch time.
Moreover, the Quit button for Front Row is very misleading for users. Indeed,
Front Row is a hidden process
so a user might wonder: "Why the hell should I quit Front Row? It's not even
running!"
That's why I think my proposed solution - using the Process Manager API and
kill(2) - is the best way to go as
it addresses both above mentioned issues: Front Row will actually be terminated
and users won't have to click
the Quit button for an application that is not running from their point of view.
Original comment by cedric.l...@gmail.com
on 4 Mar 2008 at 5:59
I'll consider adding a special option to kill the app on changes.
Original comment by j...@gmail.com
on 5 Mar 2008 at 7:15
As of Secrets 1.0.5, the problem as described in my comment #2 remains entirely.
Original comment by cedric.l...@gmail.com
on 4 Jul 2008 at 7:28
Like the Dock, Front Row relaunches even after the kill. So the ps command is
pointless.
Original comment by kestrel....@gmail.com
on 15 Feb 2010 at 12:43
As of Mac OS X 10.5.8, Front Row does not relaunches after it is killed. I have
not tested on 10.6.
Original comment by cedric.l...@gmail.com
on 15 Feb 2010 at 12:46
Original issue reported on code.google.com by
cedric.l...@gmail.com
on 3 Mar 2008 at 8:09Attachments: