"Separate units" makes using math inside inputs less usable #70010

Closed
opened 2019-09-18 11:15:22 +02:00 by Adam Preisler · 7 comments

I know this might be considered correct behavior but usually if not always I want to act on it as a whole.
The separate units are most useful for display of length and also in modifier stacks 0.5 mm looks better than 0.0005m.

First turn on separate units: Screen Shot 09-18-19 at 11.09 AM.JPG

Then move along Z axis by 1m 58cm: Screen Shot 09-18-19 at 11.09 AM 001.JPG

Now if we /2 this input it only halves the cm part: {F7755114}Screen Shot 09-18-19 at 11.09 AM 003.JPG

I know this might be considered correct behavior but usually if not always I want to act on it as a whole. The separate units are most useful for display of length and also in modifier stacks 0.5 mm looks better than 0.0005m. First turn on separate units: ![Screen Shot 09-18-19 at 11.09 AM.JPG](https://archive.blender.org/developer/F7755116/Screen_Shot_09-18-19_at_11.09_AM.JPG) Then move along Z axis by 1m 58cm: ![Screen Shot 09-18-19 at 11.09 AM 001.JPG](https://archive.blender.org/developer/F7755113/Screen_Shot_09-18-19_at_11.09_AM_001.JPG) Now if we /2 this input it only halves the cm part: {[F7755114](https://archive.blender.org/developer/F7755114/Screen_Shot_09-18-19_at_11.09_AM_002.JPG)}![Screen Shot 09-18-19 at 11.09 AM 003.JPG](https://archive.blender.org/developer/F7755115/Screen_Shot_09-18-19_at_11.09_AM_003.JPG)
Author

Added subscriber: @AdamPreisler

Added subscriber: @AdamPreisler
Member

Added subscribers: @WilliamReynish, @JacquesLucke

Added subscribers: @WilliamReynish, @JacquesLucke
Member

I'm not sure whether this should be considered a bug or a feature. With the current behavior you can do (1m 50cm)/2 to divide everything. However, if we would change the behavior to what you suggest, we could not divide individual units easily anymore. I don't really have a strong opinion on this issue though. Implementation wise, this could be a little bit tricky, but definitely solvable.

Maybe this should be treated as a feature request, not sure.

@WilliamReynish what do you think?

I'm not sure whether this should be considered a bug or a feature. With the current behavior you can do `(1m 50cm)/2` to divide everything. However, if we would change the behavior to what you suggest, we could not divide individual units easily anymore. I don't really have a strong opinion on this issue though. Implementation wise, this could be a little bit tricky, but definitely solvable. Maybe this should be treated as a feature request, not sure. @WilliamReynish what do you think?

I have no strong opinion on that. At the very least, I would probably say that this isn’t a bug, but a feature request with some new downsides.

I have no strong opinion on that. At the very least, I would probably say that this isn’t a bug, but a feature request with some new downsides.
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Jacques Lucke self-assigned this 2019-09-18 12:15:06 +02:00
Member

Closing since this is not a bug and we try to only handle bugs in the bug tracker.

Closing since this is not a bug and we try to only handle bugs in the bug tracker.
Author

It's a shame though because in 99% of cases I really don't want to divide only the cm part..

It's a shame though because in 99% of cases I really don't want to divide only the cm part..
Sign in to join this conversation.
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
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#70010
No description provided.