On Nov 14, 2008, at 15:03:40, Christopher Forsythe wrote:
> That is the standard way. One user may want one thing while another
> user may want another.
You're talking about *writing* preferences to the system-level
locations. larkost is asking for Growl to *look at* (i.e., read) the
system-level plists.
This may be the same bug/change in Mac OS X that we saw before with
GrowlMail: the standard preferences APIs fail to look at (read)
anything but the user-level preferences. As I wrote on June 18:
---
The problem is that, as of 10.5.3 (if not earlier), Mac OS X now
ignores /Library/Preferences/*.plist. The preferences we set [there]
have no effect. Thus, installing [GrowlMail] for all users wasn't
working. That's why people had to run the defaults commands themselves:
defaults write com.apple.mail EnableBundles -bool YES
defaults write com.apple.mail BundleCompatibilityVersion -int 3
Those are the same commands that our [GrowlMail] installer package
runs when you install for yourself only.
So now, we only allow you to install [GrowlMail] for yourself only on
Leopard, because that's the only way that works.
---
> If you want to set it system wide it would not be too hard to script
> that change for a sys admin.
Even better would be to support managed preferences; then, if larkost
is using Mac OS X Server, he could use the Workgroup Manager to force
some preferences. This *should* work even now, although it will
probably override any setting that a specific user sets (which may or
not be the behavior he wants).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en
-~----------~----~----~----~------~----~------~--~---
