Shown values vs actual values with hidden decimal places
Posted: Tue Aug 08, 2023 22:38
If values have additional decimal places that are not being shown, but are non zero values then the value should be marked in a red color.
In order to alleviate the additional non zero values instead of having to click in the field and manually type in the value there should be a couple of ways to address this. Middle clicking the value should immediately truncate any non zero decimal places that are currently hidden and make the shown value absolute.
Also in the alt menu at the top under "Clip" there should be an option to "Truncate all values that have non zero hidden numericals." This should also have a shortcut key to accomplish this.
One step further would be to have a global option that says sliders and values will automatically round to the nearest .xx decimal or .x decimal. Or that shown values will always be absolute (ie no hidden numericals) without any ability for in between values to be selected via the sliders unless specifically typed in. This would most likely be auto disabled for values that have automation enabled on them.
What does everyone think? Does this solve some headaches and perhaps increases workflow?
In order to alleviate the additional non zero values instead of having to click in the field and manually type in the value there should be a couple of ways to address this. Middle clicking the value should immediately truncate any non zero decimal places that are currently hidden and make the shown value absolute.
Also in the alt menu at the top under "Clip" there should be an option to "Truncate all values that have non zero hidden numericals." This should also have a shortcut key to accomplish this.
One step further would be to have a global option that says sliders and values will automatically round to the nearest .xx decimal or .x decimal. Or that shown values will always be absolute (ie no hidden numericals) without any ability for in between values to be selected via the sliders unless specifically typed in. This would most likely be auto disabled for values that have automation enabled on them.
What does everyone think? Does this solve some headaches and perhaps increases workflow?