Tool Palettes and Palette Groups

[Anonymous]

Couple of questions: 1. In the options dialog box, in the ACE Content tab, I will be pointing the Design Center to a read only network drive to share content. I assume, however, that I will need to leave the Tool Catalog path set locally so that users can customize palettes? 2. Will a tool in a "local" palette, which "points" back to a style in a network template file be updated if you Refresh the palette? 3. It appears that these network styles properties are not editable in the tool palette (such as setting height or clean up group)? What else should I know about having some things locked down on the network, while others are customizable 😉 ? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

Comments below... -- chris yanchar | product designer building solutions division | autodesk, inc. http://autodesk.blogs.com/between_the_walls/ "Reid M. Addis" wrote in message news:40572046$1_3@newsprd01... > Couple of questions: > 1. In the options dialog box, in the ACE Content tab, I will be pointing the > Design Center to a read only network drive to share content. I assume, > however, that I will need to leave the Tool Catalog path set locally so that > users can customize palettes? On the AEC Content tab, "AEC DesignCenter Content Path" serves the same purpose as in all previous releases: it points the Custom tab in DesignCenter to where the special AEC content is located. The "Tool Catalog Content Root Path" is used as a way point the tools to a central place for its dependent files. By default we install content to C:\Documents and Settings\All Users\Application Data\Autodesk\ADT 2005\enu\, but if you looked at the tool xml we ship with or if you create a tool based on a style under this root path, then you would see %AECCONTENT_DIR% substituted for that root path. For example, %AECCONTENT_DIR%\AEC Content\Imperial\Design\Conveying\Elevators\Circular.dwg. This has nothing to do with users customizing palettes locally. A user's local workspace palettes are cached to the path specified in Options > Files tab > Tool Palette File Locations. > 2. Will a tool in a "local" palette, which "points" back to a style in a > network template file be updated if you Refresh the palette? The refresh of a tool or tool palette only refreshes the tool properties or the tools contained on a palette...and only if they were brought in from a tool catalog. If a tool specifies a style from an external drawing then it will auto-import that style into the current drawing if it does not already exist, but refreshing the tool or tool palette does not overwrite styles. For that you can use Style Manager, as usual, or right-click on the tool and choose "Re-import Style". > 3. It appears that these network styles properties are not editable in the > tool palette (such as setting height or clean up group)? Correct. The idea there is that if a tool is brought in from a tool catalog, that the CAD Manager or project architect set up, and is linked back so as to offer this refreshability, then it should also be read-only as far as editing the local copy. To edit a tool that is linked to a catalog, you need to uncheck the box in the Tool Properties dialog in the very top. You can then drop it back into its source catalog to overwrite the original. Then...when others who have an instance of that tool "refresh" they will get your edits.

[Anonymous]

1. I would recommend leaving the tool palette path local. If you set the only tool palette path to a read-only [or in this case Reid-only] network location, then the users will only get the palettes/tools you place there and will not be able to create their own. The refresh feature or the auto-refresh feature should be sufficient to assure that network-based office standards are up to date. If you absolutely had to put the tool palette path to a network, then add a second, local path so the users can set up custom palettes for on-the-fly, just-for-today use.

2. If the local palette was created using the Content Browser, pulling from a network-based Tool Catalog [which can be in a read-only directory], and the palette was left as refreshable [the default] or set to auto-refresh, then refreshing the palette will update it with any changes made to the catalog. Note also that for style-based tools or AEC Content based tools, the tool itself merely holds a reference to the source file [which, for office standard stuff, is probably also in a read-only network location]. If you update that source file, then the updated style/AEC Content file will be referenced by the tool on its next use - provided that the style/AEC Content does not already exist in the target drawing file. [Use the "Reimport" option on the tool's right click menu to redefine the style/AEC Content in this case.] You do not need to update the tool every time the source file is updated [provided the file location, file name, style/content name remain the same].

3. If any tool palette or tool is set to be refreshable - whether the source location is local/editable or network/read only - the palette/tool properties will not be editable. If a user has a "limited" need to customize an office standard tool that does not merit adding that version of the tool to your office catalog, the office standard tool can be copied and pasted onto an editable tool palette [create a new one, if necessary]. Then edit the properties, uncheck the refresh toggle and edit away. That tool is now its own creature and will not pick up any changes to the original tool in the catalog; it does still point back to the same source file, so any style/content revisions would follow through.

--

David Koch
Autodesk Discussion Group Facilitator

[Anonymous]

Thanks Chris. So, I'm still confused about >>The "Tool Catalog Content Root Path" is used as a way point the tools to a central place for its dependent files. << What I want to be able to do is keep users from deleting or altering "office standard" tool palettes, while allowing them to create their own custom ones. Is it possible to do this? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

Reid The term 'central place for its dependent files' might be better stated as a 'default place...' since it's possible to create catalogs that contain absolute references to dependent files. Using a network scenario, one where users access office 'standards' from a central location, it's fairly easy to accomplish what you're describing. You would publish a standard set of style drawings to a network location using Content Browser's Publish facility to describe where those 'standard' dependent files are placed. Neither you nor the users would have to change the "Tool Catalog Content Root Path" since your posted catalog would contain 'hard references' to the dependent files. Users would still be free to create tools based on styles on their local Content folder. Does that answer your question? Dave Stroud Software Engineer Building Solutions Division | Autodesk, Inc. "Reid M. Addis" wrote in message news:4058bff8_3@newsprd01... > Thanks Chris. > So, I'm still confused about >>The "Tool Catalog Content Root Path" is used > as a way point the tools to a central place for its dependent files. << > What I want to be able to do is keep users from deleting or altering "office > standard" tool palettes, while allowing them to create their own custom > ones. Is it possible to do this? > > -- > Regards, > --------------- > Reid M. Addis > Registered Architect > Architectural Applications Specialist > Granary Associates > 411 North 20th Street > Philadelphia, PA 19130 > Ph. 215-665-7056 > email: addis@granaryassoc.com > >

[Anonymous]

Probably, but I'm dense today ;) What would I do exactly? Where are the "office standard tool palettes" stored, and what are they exactly? Are they an XML file, or an ACS file? What do I adjust in the Options dialog box? Again, the goals are as follows: 1. Everyone gets the office Standard Set of Tool Palettes and Palette Groups 2. The items in Number 1 may not be Deleted, or altered, meaning you can't delete a Wall Style from the office standard Walls tool palette 3. Every user should be capable of creating their own tool palette(s) within either an office standard palette group, or create their own palette group(s) 4. When I add either a palette or group to the office standard tool palette, everyone's tool palette will be updated to reflect this - automatically. Thanks! -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

I believe that you are asking for something that I currently do here in my office. I have set up the following: On a network server, located within a permissions protected folder, I have added a new catalog by right clicking in the Content Browser window. When given the choice of a creating new catalog, or add an existing catalog I choose to create a new catalog (see attached image). I then browse to the directory that only administrators have write access to, and create a new catalog there with the name that I want. I then add categories, packages, and or palettes to the catalog. After all work in the new catalog is complete, I then open the existing catalog on the user's computer. The use can then drag and drop the palettes onto their computer. These palettes with tools are refreshed from the server by "read only" default because they are on the server, and not on the local computer. When I update the catalog or palette, I just send out an email letting everyone know to refresh their palettes. Everyone is then updated. Seems to work well for me. So far I have 10 people accessing the same catalog. I can also copy the folder on the server to disk, take to a remote location, and on that computer add the catalog to the Content Browser and all works well. Hope this helps a little. Keith White "Reid M. Addis" wrote in message news:4059c036$1_1@newsprd01... Probably, but I'm dense today ;) What would I do exactly? Where are the "office standard tool palettes" stored, and what are they exactly? Are they an XML file, or an ACS file? What do I adjust in the Options dialog box? Again, the goals are as follows: 1. Everyone gets the office Standard Set of Tool Palettes and Palette Groups 2. The items in Number 1 may not be Deleted, or altered, meaning you can't delete a Wall Style from the office standard Walls tool palette 3. Every user should be capable of creating their own tool palette(s) within either an office standard palette group, or create their own palette group(s) 4. When I add either a palette or group to the office standard tool palette, everyone's tool palette will be updated to reflect this - automatically. Thanks! -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

Thanks! Can your users delete standard tools from the palettes once they are on the local station? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

No. When I right click on the tool, delete is not an option. See attached image. Keith White "Reid M. Addis" wrote in message news:4059eab2_1@newsprd01... Thanks! Can your users delete standard tools from the palettes once they are on the local station? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

The tool is refreshable, meaning that it has a back link to the catalog. Tools with such a link are, by definition, read only. You can make the item editable by opening the tool properties and unchecking "Refresh from..." 'breaking' the link, and making the tool editable. cheers Mark "Keith White" wrote in message news:4059f54d_3@newsprd01... No. When I right click on the tool, delete is not an option. See attached image. Keith White "Reid M. Addis" wrote in message news:4059eab2_1@newsprd01... Thanks! Can your users delete standard tools from the palettes once they are on the local station? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email: addis@granaryassoc.com

[Anonymous]

what if the "refresh from" box is grey'd out and uncheckable?  why will this palette not refresh?  the "source file" location is correct, and has been updated, but my tool palette will not grab the new information.  

My "source file" is on a separate server than i am working in.  

there has GOT to be a simple way to tell Autocad, to "reload" all the palettes.... why is this so difficult?  I'm working in Architecture 2009.

[David_W_Koch]

Is the grayed out "Refresh from" toggle in the properties of a palette or the properties of an individual tool?  If a palette, then the palette itself is no longer connected to a palette in a tool catalog.  (If the original catalog is still there, and has a palette of the same name, it is possible that the original palette was deleted and replaced with another of the same name.  That matters to ACA - it does not just go by the palette name, and adding a new palette rather than updating the old will break the refresh link.)

If it is just an individual tool on a refreshable palette, you should be able to refresh the entire palette and get any changes made to the tool.

[Anonymous]

here is the screen shot form the palette properties box.




Leilani Gnall-Gregory

Senior Project Manager

WHA | William Hezmalhalch Architects, Inc.

5000 Executive Parkway, Suite 375

San Ramon, CA 94583

Direct: (925) 627-1178

LeilaniG@whainc.com


Leilani Gnall-Gregory
Senior Project Manager
WHA | William Hezmalhalch Architects, Inc.
5000 Executive Parkway, Suite 375
San Ramon, CA 94583
T (925) 627-1178
F (949) 250-1529

Start chatting on our blog: blog.wharchitects.com
Visit our website: www.wharchitects.com


CONFIDENTIALITY: The information contained in this e-mail, including any accompanying documents or attachments, is from William Hezmalhalch Architects, Inc. (WHA), is intended only for the use of the individual or entity named above, and is privileged and confidential. If you are the intended recipient of this e-mail, then by utilizing the information contained in this e-mail, you agree that such information may not be compatible with your software; further, you agree to use such information only for the purpose or project for which it was intended, and, to the full extent provided by California law, agree to release and indemnify WHA and its affiliated entities and individuals for all damages arising out of any such misuse of the information. If you are not the intended recipient of this e-mail, be aware that any disclosure, dissemination, distribution, copying or use of the contents of this message is strictly prohibited. If you have received this e-mail in error, please notify us by telephoning Lorrie Gagne at (949) 250-0607, return the e-mail message, and destroy (delete) the original.

[David_W_Koch]

The screen capture was not attached to your post.