The Navigation Gizmo does not distinguish between the +ve and -ve direction of all three axes #76120

Closed
opened 2020-04-26 12:56:03 +02:00 by Narayan Aras · 7 comments

Try this:

**Step-1:**Turn the Navigation Gizmo so that we can see all six circles.
image.png

Step-2: Click on the dark red circle. (+ve x-axis)

Step-3: Repeat Step-1

Step-4: Click on the light red circle (-ve x-axis)

The Navigation Gizmo looks practically similar in steps 2 and 4. There is a very small difference in the diameter of the circles, but this is not easily discernible.

If we repeat the experiment with the other axes, the same problem can be observed.

Desirable:
Make the difference easily discernible.
For example, let the negative axes have hexagons or squares instead of circles.
Or let them have a white line border, like this: image.png

Try this: **Step-1:**Turn the Navigation Gizmo so that we can see all six circles. ![image.png](https://archive.blender.org/developer/F8495946/image.png) **Step-2:** Click on the dark red circle. (+ve x-axis) **Step-3:** Repeat Step-1 **Step-4:** Click on the light red circle (-ve x-axis) The Navigation Gizmo looks practically similar in steps 2 and 4. There is a very small difference in the diameter of the circles, but this is not easily discernible. If we repeat the experiment with the other axes, the same problem can be observed. **Desirable:** Make the difference easily discernible. For example, let the negative axes have hexagons or squares instead of circles. Or let them have a white line border, like this: ![image.png](https://archive.blender.org/developer/F8495949/image.png)
Author

Added subscriber: @raindrops

Added subscriber: @raindrops
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Right hand rule to the rescue ;)

Right hand rule to the rescue ;)
Author

I know what you mean: From the remaining two axes, we can always infer whether we are looking at the +ve or -ve of an axis.
However, for this to work, we have to know all the combinations by heart.
It's not simple at all!

Therefore, it is best to have this explicit difference.

I know what you mean: From the remaining two axes, we can always infer whether we are looking at the +ve or -ve of an axis. However, for this to work, we have to know all the combinations by heart. It's not simple at all! Therefore, it is best to have this explicit difference.

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Richard Antalik self-assigned this 2020-04-28 19:29:02 +02:00

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. 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

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. 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 For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Narayan Aras changed title from The widget does not distinguish between the +ve and -ve direction of all three axes to The Navigation Gizmo does not distinguish between the +ve and -ve direction of all three axes 2020-04-30 11:09:46 +02:00
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#76120
No description provided.