tool palette issue
I am assuming that you are setting this up for a number of other users and not just for yourself, and that the location where you store the palettes is read-only to the other users. If that is the case, then why do the palettes need to be refreshable for other users?
Palettes in my office are set up with the Tool Palettes File Locations pointing to the network folders where the Tool Catalogs are stored. Three of us in the design technology support group have write access to those folders; typical users on the floor do not, and the palettes are "locked". When changes need to be made to an existing palette, I switch to a profile on my computer where I do not have the Tool Palettes File Locations pointing to the Tool Catalogs folders and where I have, instead, used Content Browser to add refreshable local versions. I turn off refreshability, edit the contents of the palette as needed, drag the palette back to the catalog and replace the previous version and then turn refreshability back on. If the changes stick, I know I did it right and then next time someone opens the program, they will have the revised version of the palette.
That makes it easy to set everyone up (when they remember to use the correct profile) and I only have to deal with refreshable palettes on my computer, and then only when I am making changes. Most of the time, I work in a profile that is set up the same way as everyone else, with the locked palettes.
@tevansHMH wrote:
So let me repeat back what I hear is the way you set them up. Your day to day profile has your palette file path in it as well as all of your other users. You have another profile that does not. When you want to add or remove content from a palette you switch to the profile that doesn’t have the file path in it, make the palette you want to make changes to not refreshable, make the changes, drag it to content browser and then set it back to refreshable and switch to your regular profile. The palettes will update when you close and reopen ACA?
That sounds correct, and, yes, when I switch back to my "typical user" profile, the changes are there, since ACA is reloading the palettes on the profile change. I am not 100% certain what the other users experience, but I believe they would have to either close/reopen ACA -OR- change to a profile with different paths, and then back again. The key is to not delete the palette and then add a revised one, if you use Tool Palette Groups (which we do). A new palette will show up in "All Palettes", but would have to be added to the appropriate Tool Palette Group(s) on each machine. We have done that in the past, emailing detailed instructions on how to add the new palettes to the appropriate Group. Most got it, but I was manually adding the missing palettes for users for weeks afterwards. Unavoidable in that case, as they were brand new palettes, but for updates to an existing palette, even if I have to remove every single tool and rebuild the palette completely, I still want to do so in the existing palette.
@tevansHMH wrote:
When you add a new palette do you create it in ACA and drag it to Content Browser or do you create the Palette in Content Browser then just drag the content to the palette from ACA?
For a totally new palette, either method should work; I would probably create it locally and then add it to the Catalog in Content Browser.
Yes, you will need to use Content Browser to add the desired tool palettes from your Catalog. Before doing so, check your Catalog's properties and verify that the Link items when added to workspace toggle is checked, so that they will be added as refreshable palettes.
