UI - merge vertices hotkey sequence should not depend on selection method #84335

Closed
opened 2021-01-02 23:40:41 +01:00 by Dodger Cannon · 7 comments

System Information
Operating system: All systems
Graphics card: N/A

Blender Version
Broken: 2.83.5
Worked: N/A

Short description of error
When merging vertices (M hotkey), the subsequent hotkey for how to merge changes depending on selection, not in a way relevant to the selection.

Exact steps for others to reproduce the error
Select three vertices, one at a time, so that there is a selection active (i.e. so there is a white vertex under standard interface). Press M to merge. Note that the options are: A: At First, L: At Last, C: At Centre, T: At Cursor, O: Collapse.

Now select none and then select three vertices, such that none of them is the active selection, e.g. by a box/marquee selection (what used to require and still can use the B key) or by selecting a face in face mode or edge in edge mode. Press M to merge. Note that the options are: A: At Centre, C: At Cursor, O: Collapse

Reasonable expectation would be that after pressing M to merge vertices, A and C would always do the same thing, and that the semantic relationships between the keys/letters and the effects thereof would maintain consistency.

Recommendation:
Make the following sequences consistent:
C: At Centre
T: At Cursor
O: Collapse

With the following two options added when a primary specific selection is in effect:
F: At First
L: At Last

This way, regardless of the way the selections are made, the subsequent merging can maintain the same exact workflow except when "At First" or "At Last" is desired, those requiring the active selection approach.

**System Information** Operating system: All systems Graphics card: N/A **Blender Version** Broken: 2.83.5 Worked: N/A **Short description of error** When merging vertices (M hotkey), the subsequent hotkey for how to merge changes depending on selection, not in a way relevant to the selection. **Exact steps for others to reproduce the error** Select three vertices, one at a time, so that there is a selection active (i.e. so there is a white vertex under standard interface). Press M to merge. Note that the options are: A: At First, L: At Last, C: At Centre, T: At Cursor, O: Collapse. Now select none and then select three vertices, such that none of them is the active selection, e.g. by a box/marquee selection (what used to require and still can use the B key) or by selecting a face in face mode or edge in edge mode. Press M to merge. Note that the options are: A: At Centre, C: At Cursor, O: Collapse Reasonable expectation would be that after pressing M to merge vertices, A and C would always do the same thing, and that the semantic relationships between the keys/letters and the effects thereof would maintain consistency. Recommendation: Make the following sequences consistent: C: At Centre T: At Cursor O: Collapse With the following two options added when a primary specific selection is in effect: F: At First L: At Last This way, regardless of the way the selections are made, the subsequent merging can maintain the same exact workflow except when "At First" or "At Last" is desired, those requiring the active selection approach.
Author

Added subscriber: @Dodger-1

Added subscriber: @Dodger-1
Member

Added subscribers: @HooglyBoogly, @filedescriptor

Added subscribers: @HooglyBoogly, @filedescriptor
Member

I can confirm the problem, but wouldn't consider it a bug. I will tag it as a papercut. Maybe @HooglyBoogly is interested?

I can confirm the problem, but wouldn't consider it a bug. I will tag it as a papercut. Maybe @HooglyBoogly is interested?
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Hans Goudey was assigned by Falk David 2021-01-05 18:58:24 +01:00
Member

Thank you @HooglyBoogly for taking a look and making a patch!

Thank you @HooglyBoogly for taking a look and making a patch!

This issue was referenced by bc0e121bce

This issue was referenced by bc0e121bce257a8ea9d7855b074a7a22a8c3699b
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: '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#84335
No description provided.