<[email protected]> wrote: >Would it be feasible to have all the 4 possibilities ? (set to true by default >and user can change, force to true, set to false by default and user can >change, force to false) >It would be great!
I'm a big fan of options too, and letting the organization determine how important control of a particular setting should be. Microsoft has a number of Group Policy settings with five values relating to a boolean parameter: Unset, which lets the documented default chain of priorities determine the eventual setting of that parameter, plus something like the above four values that could allow the organization to determine whether the user is allowed to set a different value. If the user setting should be temporary (user cannot save this setting) and the Policy setting always imposed on program load or restart, then two additional values are needed for a total of seven. For a string value, perhaps a prefix character would serve: "https://example.org/"; = default, user can change "!https://example.org/"; = fixed, user cannot change "*https://example.org/"; = default, user can change, reset on restart Or are there wheels with fewer corners already in use? _______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
