Select to view content in your preferred language

Add/Remove Units to ALL projects (global setting)

120
2
Wednesday
Status: Open
Labels (1)
AlfredBaldenweck
MVP Frequent Contributor

Pro 3.5

I have a workflow for my users that sets their user settings to match our office's best practices (e.g. default toolbox or lack thereof, etc.)

I'd like to be able to set the units they have available to them across all projects. 

For example, we do not want them using the US Survey Foot and its derived units (US Survey Acres, etc.)

Similarly, in this other Idea posted the other day, it would probably make sense for this user to always have Nautical Miles available.

Please enact a global option for units (maybe it can get overridden by project-level units?)

2 Comments
AyanPalit

@AlfredBaldenweck Have you tried setting the default units in Pro > Project > Options > Units

AyanPalit_0-1768441643133.png

I believe the current behavior is to preserve the default settings until you change them. Please clarify if this is not what you are looking for. 

Are you looking for a global application settings ?

 

AlfredBaldenweck

Yes, that is what prompted this post. Those settings as currently offered are applied per project, meaning that that entire tab of the options menu is inaccessible if you open without a project and are not applied globally.

For example, to test this this morning, I created a new project and added Chains to the distance units. I saved the project and created a second new project. Chains were not in the distance units for the second project.

If I have a business need that requires me to always use a specific unit, such as Chains or Nautical Miles, I should not have to open the settings to add the unit every time I make a new project. Similarly, if I want to make sure I'm not using the wrong version of a unit (US Survey Foot vs International Foot), I want to programmatically remove the wrong version of the unit from all my projects.

 

I do understand the need for a project-level unit collection and don't think it should go away. But that does not mean that we shouldn't be able to have a global setting. My vote is for the setting to live in user.config instead of in Pro.settingsConfig/the registry.