Skip to main content
1-Visitor
August 1, 2014
Question

checking preferences via ACL

  • August 1, 2014
  • 18 replies
  • 3343 views

How would one checkthe value of apreference setting with ACL? I assume there is some kind of prefix required.
For example, I want to know whether peservices is on or off and


message peservices


doesn't work.

    18 replies

    1-Visitor
    August 5, 2014

    I use a "belt and suspenders" approach to keeping users' desired preferences set.



    if (doc_type()=='chapter'||doc_type()=='section') {


    _docload::chapter_menus();


    } else if ...



    from the command line to check them.


    lou.argyres@ceb.ucla.edu | ceb.com


    UNIVERSITY OF CALIFORNIA • STATE BAR OF CALIFORNIA




    In Reply to Caroline Leccese:



    Thanks, Paul and Lynn!


    Instance.acl seems to work, when put in the doctype folder.


    18-Opal
    August 5, 2014
    Also, see the help center topic for write_preferences() for information on how to push programmatically defined preference values into the user preferences file.

    --Clay
    1-Visitor
    August 5, 2014
    I always wanted to prepare an anti-presentation to Charles' Tips and Tricks
    that demonstrated all of the countermeasures we "environment
    administrators" can take to prevent our beloved authors from getting into
    trouble (especially the kind that triggered 3-a.m.-production-run support
    calls).

    Removing access to the Preferences Dialog is a perfect example of same.

    I had a cute name in mind for the preso but apparently those neurons are on
    break ...



    On Tue, Aug 5, 2014 at 9:07 AM, Lou Argyres <->
    wrote:

    > I use a "belt and suspenders" approach to keeping users' desired
    > preferences set.
    >
    > Use a blank menu file from which Tools.Preferences has been removed;
    > that's set by an APTMENUFILE environment variable. (There's also an init
    > "map all shift-control-alt-0 ... { source showprefsdlg.acl }" back door for
    > showing Preferences dialog . The init file also turns off the Command
    > window based on APTRC.)
    >
    > A central script sets all user preferences and is called from relevant
    > instance.acl files. Further menu/environment settings are located in an
    > editinit ACL and called by the preferences script based on doctype.
    >
    > if (doc_type()=='chapter'||doc_type()=='section') {
    >
    > _docload::chapter_menus();
    >
    > } else if ...
    >
    > It's important to note that preference modifications by command are not
    > necessarily reflected in real time in the Preferences dialog, so use smthg
    > like
    >
    > response(option("changetracking"))
    >
    > from the command line to check them.
    >
    > Lou Argyres
    >
    > CEB / Continuing Education of the Bar
    >
    > lou.argyres@ceb.ucla.edu | *ceb.com*
    1-Visitor
    August 5, 2014
    Isn't the problem that you likely need to give authors the ability to control some preferences but not others?

    It's unfortunate that preferences can't be divided into 'personal' and 'environment' categories, the first being accessible to the authors and the second to just the system administrator.

    Having all preferences lumped into one file seems to be the issue.

    David

    David S. Taylor

    Project Manager, Production and Marketing
    Building Regulations | NRC Construction
    National Research Council Canada
    Building M-23A, Room 114 | 1200 Montreal Road | Ottawa, ON | K1A 0R6
    Telephone: +1.613.990.2731 | Fax: +1.613.952.4040
    David.S.Taylor@nrc-cnrc.gc.ca<">mailto:David.S.Taylor@nrc-cnrc.gc.ca>

    1-Visitor
    August 5, 2014
    Charle's and I did a 'Tips and Tricks' at one AUGI. He gave the Arbortext
    line and I gave the work around. It was fun. 😄



    Lynn


    1-Visitor
    August 5, 2014
    True, but like so many other things, which preferences would go where? So
    unless the individual program admin could determine it might be difficult to
    implement.



    Lynn


    1-Visitor
    August 5, 2014
    I would have liked to have seen that!


    On Tue, Aug 5, 2014 at 10:25 AM, Lynn Hales <->
    wrote:

    > Charle's and I did a 'Tips and Tricks' at one AUGI. He gave the Arbortext
    > line and I gave the work around. It was fun. Smiley Very Happy
    >
    >
    >
    > Lynn
    >
    >
    >
    > *From:* Paul Nagai [
    > administrators" can take to prevent our beloved authors from getting into
    > trouble (especially the kind that triggered 3-a.m.-production-run support
    > calls).
    >
    > Removing access to the Preferences Dialog is a perfect example of same.
    >
    > I had a cute name in mind for the preso but apparently those neurons are
    > on break ...
    >
    >
    >
    >
    >
    > On Tue, Aug 5, 2014 at 9:07 AM, Lou Argyres <->
    > wrote:
    >
    > I use a "belt and suspenders" approach to keeping users' desired
    > preferences set.
    >
    > Use a blank menu file from which Tools.Preferences has been removed;
    > that's set by an APTMENUFILE environment variable. (There's also an init
    > "map all shift-control-alt-0 ... { source showprefsdlg.acl }" back door for
    > showing Preferences dialog . The init file also turns off the Command
    > window based on APTRC.)
    >
    > A central script sets all user preferences and is called from relevant
    > instance.acl files. Further menu/environment settings are located in an
    > editinit ACL and called by the preferences script based on doctype.
    >
    > if (doc_type()=='chapter'||doc_type()=='section') {
    >
    > _docload::chapter_menus();
    >
    > } else if ...
    >
    > It's important to note that preference modifications by command are not
    > necessarily reflected in real time in the Preferences dialog, so use smthg
    > like
    >
    > response(option("changetracking"))
    >
    > from the command line to check them.
    >
    > Lou Argyres
    >
    > CEB / Continuing Education of the Bar
    >
    > lou.argyres@ceb.ucla.edu | *ceb.com*
    1-Visitor
    August 5, 2014

    There's a further level of preferences related to dialogs that I unfortunately *cannot* access, even though they cry out.


    <property>


    <name>com.ptc.arbortext.changetracking.highlightchange</name>


    <value><string>1</string></value>


    </property>


    http://communities.ptc.com/ideas/3348


    Lou Argyres


    CEB / Continuing Education of the Bar


    lou.argyres@ceb.ucla.edu | ceb.com


    UNIVERSITY OF CALIFORNIA • STATE BAR OF CALIFORNIA