On May 19, 2:53 am, Peter Hosey <[email protected]> wrote: > On May 18, 2010, at 20:18:20, sourcehound wrote: > > > … add a "Lock" and use the Security Framework to require authentication to > > change any settings in Growl. … > > > It's really simple. > > I assure you that implementing authorization for anything is the opposite of > simple. > > As far as I can tell from the docs, this feature is impossible. Quoth the CF > Preferences Utilities documentation: > > > [CFPreferencesAppValueIsForced returns] true if value of the key cannot be > > changed by the user, otherwise false. > > “cannot be changed”. This implies that it is flat-out impossible for the user > to change any preference that is set from on high. >
Peter, since you can disable a System Preference Pane entirely as part of the standard feature set of Workgroup Manager, then it's not really necessary for the Growl Dev Team to do anything except implement the white list and notify the user. I agree with you that, once in place, the whitelist should not be overridden by managed users. The suggestion to use SFAuthorizationView was unnecessary, sorry. -- 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.
