python - max property precision is showing unused digits. #112309

New Issue

michael campbell · 2023-09-13T02:29:26+02:00

michael campbell commented

2023-09-13 02:29:26 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99

Blender Version
Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-05 15:07, hash: d371c3c09fa8

I'm not 100% sure this is a bug, but the user manual suggest a property's precision attribute is used to set the maximum number of digits that can be shown, however when specifying a property's precision value to 6 and then setting that value to 0.1 in the user interface, the display shows 0.100000 rather than the expected 0.1 (the necessary digits)

https://docs.blender.org/api/current/bpy.props.html#:~:text=precision)%20property%20definition.-,Parameters,-name%20(string

It takes up unnecessary space on sliders, obscuring the property name.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99 **Blender Version** Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-05 15:07, hash: `d371c3c09fa8` I'm not 100% sure this is a bug, but the user manual suggest a property's precision attribute is used to set the maximum number of digits that can be shown, however when specifying a property's precision value to 6 and then setting that value to 0.1 in the user interface, the display shows 0.100000 rather than the expected 0.1 (the necessary digits) https://docs.blender.org/api/current/bpy.props.html#:~:text=precision)%20property%20definition.-,Parameters,-name%20(string ![image](/attachments/d3824b55-5be6-46f8-94a4-28735b04f74a) ![image](/attachments/8d0275a4-0ab0-481d-9a0b-0fa583b8b0c7) It takes up unnecessary space on sliders, obscuring the property name.

image.png

4.1 KiB

image.png

6.3 KiB

michael campbell added the

labels 2023-09-13 02:29:27 +02:00

michael campbell commented

2023-09-13 03:00:57 +02:00

On a side note. I notice when no precision is set, the number of decimal places shown behaves differently if you enter 0.0000001 than if you enter 0.1234567

entering:

shown:

editing:

different if there are no zeros before the first populated decimal place

entering:

shown:

editing:

On a side note. I notice when no precision is set, the number of decimal places shown behaves differently if you enter 0.0000001 than if you enter 0.1234567 entering: ![image](/attachments/c2d29b26-c794-4a29-9c50-512cc7297771) shown: ![image](/attachments/02acfceb-73ce-4e5d-8973-8ba95c6ea5b4) editing: ![image](/attachments/526f72f2-46ba-4ec7-931c-f222e0fc3e88) different if there are no zeros before the first populated decimal place entering: ![image](/attachments/577bb89d-9beb-4d5f-84b3-35678126f473) shown: ![image](/attachments/660bf8d5-eb36-487a-b7b4-7059e588c998) editing: ![image](/attachments/a5ba53b4-539c-4afd-941a-957a4f8fe5e3)

image.png

4.5 KiB

image.png

5.6 KiB

image.png

2.5 KiB

image.png

2.3 KiB

image.png

1.8 KiB

image.png

2.7 KiB

Germano Cavalcante commented

2023-09-13 04:06:53 +02:00

Thanks for the report, but this behavior is old, the code is about 12 years old.

You can see the history and changes involved in this area in these commits:
0d7b3ed39c (RNA: display exact integer values without fraction if step is integer)
d5c9b509ec (Fix issues with float precision in numinput, like 'R 123' who would show additional 'noise' digits)
152b06dc82 (use a better method for finding the precision to use for float buttons...)
06c3756db8 (smarter precision calculation, so 0.000001 isn't displayed as 0.00)

If the design really needs improvement, it would be necessary to start a discussion with the UI team.

Unfortunately, we cannot confirm this report, as it is a request for modified/improved behavior and not really a bug in current behavior. So closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

If, after being communicated, the UI team decides that this is an area that needs to be reviewed, this report can be reopened.

Thanks for the report, but this behavior is old, the code is about 12 years old. You can see the history and changes involved in this area in these commits: 0d7b3ed39c (RNA: display exact integer values without fraction if step is integer) d5c9b509ec (Fix issues with float precision in numinput, like 'R 123' who would show additional 'noise' digits) 152b06dc82 (use a better method for finding the precision to use for float buttons...) 06c3756db8 (smarter precision calculation, so 0.000001 isn't displayed as 0.00) If the design really needs improvement, it would be necessary to start a discussion with the UI team. Unfortunately, we cannot confirm this report, as it is a request for modified/improved behavior and not really a bug in current behavior. So closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests If, after being communicated, the UI team decides that this is an area that needs to be reviewed, this report can be reopened.

Germano Cavalcante closed this issue

2023-09-13 04:06:55 +02:00

Blender Bot added

and removed

labels 2023-09-13 04:07:53 +02:00

michael campbell commented

2023-09-13 04:35:53 +02:00

Thanks 👍