Units display visual bug (rounding to integer) #70367
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#70367
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 7
Graphics card: RX270
Blender Version
Broken: 2.8 and 2.81 (sub 12), branch: master, commit date: 2019-09-29 06:28, hash:
ba90d2efa5
Worked: (optional)
Short description of error
Properties of some operators are displayed rounded
Exact steps for others to reproduce the error
General
templateProperties in last action area are rounded to whole number, while properties in side panel are rounded to 1 decimal place
Added subscriber: @APEC
Added subscribers: @WilliamReynish, @JulianEisel, @JacquesLucke, @lichtwerk
I agree this looks like an unneccessary inconsistency [compared to how it is displayed elsewhere...].
CC @WilliamReynish
CC @JacquesLucke
CC @JulianEisel
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
Added subscribers: @ideasman42, @brecht
Would propose this as a fix: P1209: Potential fix for #70367
@ideasman42, @brecht, objections?
This issue was referenced by
003be8aa7c
Changed status from 'Confirmed' to: 'Resolved'
Went ahead and pushed the proposed fix.
Note that this isn't a bug strictly speaking, just a visual inconsistency. It also increases the visual precision quite a bit for other units - but since we already use the same precision elsewhere, I think it's good to make them match.
Can I open this again?
Yes it now visually have the same numbers, but it incorrect because rounding to integer is still exist.
You might think 0.5 mm its a nothing, but in 3d modeling app it's a huge difference between 65 mm and 65.5mm.
However in Edit Mode it show correct position coordinate numbers, but incorrect edge length.
It's still a visual inconsistency.
The same thing is for degree angles.
Tell me, maybe I'm writing in vain here? And do I need to create a new request?
there should be strict specificity in this question, to what number after the decimal point should the value be rounded.
Example how it's look in Modo. It rounding to the fourth number after the decimal point in all values if there are more than four numbers.