Transform Modal Map - double entry Automatic Constraint #82423

Closed
opened 2020-11-05 09:49:57 +01:00 by Reiner Prokein · 18 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.43

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-01 08:11, hash: a1f46ac9dc
Worked: (newest version of Blender that worked as expected)

Short description of error
The automatic constraint in the transform modal map is doubled

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Open Blender, move the default cube, watch the footer. Two entries for Automatic Constraint.

There are also two entries in the modal keymap and in the property value popup.

automatic1.jpg

automatic2.jpg

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.43 **Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-01 08:11, hash: `a1f46ac9dc` Worked: (newest version of Blender that worked as expected) **Short description of error** The automatic constraint in the transform modal map is doubled **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] Open Blender, move the default cube, watch the footer. Two entries for Automatic Constraint. There are also two entries in the modal keymap and in the property value popup. ![automatic1.jpg](https://archive.blender.org/developer/F9206243/automatic1.jpg) ![automatic2.jpg](https://archive.blender.org/developer/F9206245/automatic2.jpg)
Author

Added subscriber: @tiles

Added subscriber: @tiles

Added subscriber: @rjg

Added subscriber: @rjg

This appears to be caused by the following two enum property items in transform_modal_keymap (transform.c) that have the same display name:

      {TFM_MODAL_AUTOCONSTRAINT, "AUTOCONSTRAIN", 0, "Automatic Constraint", ""},
      {TFM_MODAL_AUTOCONSTRAINTPLANE, "AUTOCONSTRAINPLANE", 0, "Automatic Constraint", ""},

I think the second one should be renamed to "Automatic Constraint Plane".

This appears to be caused by the following two enum property items in `transform_modal_keymap` (`transform.c`) that have the same display name: ``` {TFM_MODAL_AUTOCONSTRAINT, "AUTOCONSTRAIN", 0, "Automatic Constraint", ""}, {TFM_MODAL_AUTOCONSTRAINTPLANE, "AUTOCONSTRAINPLANE", 0, "Automatic Constraint", ""}, ``` I think the second one should be renamed to "Automatic Constraint Plane".

Added subscriber: @mano-wii

Added subscriber: @mano-wii

This entry was create by ba014586a0.
@mano-wii Based on the commit message I'm not sure if the same name was intentional?

This entry was create by ba014586a0. @mano-wii Based on the commit message I'm not sure if the same name was intentional?
Author

Ah, i see. So the one is meant to move along an axis, the other to move along a plane. The second one doesn't really work well though, tried it with another hotkey. And this needs of course also another hotkey then. Both have at the moment mmb assigned.

Ah, i see. So the one is meant to move along an axis, the other to move along a plane. The second one doesn't really work well though, tried it with another hotkey. And this needs of course also another hotkey then. Both have at the moment mmb assigned.

@tiles They already have different shortcuts by default, one is {key MMB} and one is {key Shift MMB}. Apparently the {key Shift} isn't displayed in the status bar though. While it was using shift in the referenced commit, the shortcut was changed in another one.

@tiles ~~They already have different shortcuts by default, one is {key MMB} and one is {key Shift MMB}. Apparently the {key Shift} isn't displayed in the status bar though.~~ While it was using shift in the referenced commit, the shortcut was changed in another one.
Author

It's also not displayed in the keymap :)

It's also not displayed in the keymap :)
Author

Just tested. I can't get this arrow up +mmb hotkey combination to work. It constraints still along the single axis.

Just tested. I can't get this arrow up +mmb hotkey combination to work. It constraints still along the single axis.

This comment was removed by @rjg

*This comment was removed by @rjg*
Author

And shift conflicts with precision movement then. Seems that we found a can of worms here ^^

And shift conflicts with precision movement then. Seems that we found a can of worms here ^^

@tiles I'm sorry, I was wrong. It was using Shift in the referenced commit, but has been removed in f5080c82dd. I think this was by accident though, as the commit message states that it intended to only remove the "repeat".

@tiles I'm sorry, I was wrong. It was using Shift in the referenced commit, but has been removed in f5080c82dd. I think this was by accident though, as the commit message states that it intended to only remove the "repeat".

In #82423#1048942, @tiles wrote:
And shift conflicts with precision movement then. Seems that we found a can of worms here ^^

This is a well-known old conflict.
I don't know whose idea it was, but it has already been established that way.

> In #82423#1048942, @tiles wrote: > And shift conflicts with precision movement then. Seems that we found a can of worms here ^^ This is a well-known old conflict. I don't know whose idea it was, but it has already been established that way.

This issue was referenced by 7fed420877

This issue was referenced by 7fed420877bd22a0f0745353ba6a992d6c05a6f4

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

Changed status from 'Needs Triage' to: 'Resolved'
Robert Guetzkow self-assigned this 2020-11-05 21:31:48 +01:00

I'll add the "Shift" back in a second commit in just a moment.

I'll add the "Shift" back in a second commit in just a moment.

This issue was referenced by ad481bdd35

This issue was referenced by ad481bdd354bc82ac32866240bf816d2abdbb608
Author

Many thanks for fixing. Why not use Alt here? Then this old conflict would be resolved :)

Many thanks for fixing. Why not use Alt here? Then this old conflict would be resolved :)
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
4 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#82423
No description provided.