Fix #108096: UI: copy-paste buttons can change source properties #108270

Merged
Philipp Oeser merged 3 commits from lichtwerk/blender:108096 into blender-v3.6-release 2023-06-07 11:19:10 +02:00
Member

Pasting numerical array buttons happens with Ctrl + Alt + V.
Holding Alt also triggers uiSelectContext, so having other nodes/
objects etc. selected while doing this would try to copy the pasted
values back to other objects (possibly to the ones you pasted from) and
that happens relative to the original value, so the value actually
changes.

NOTE: the Ctrl + Alt + V shortcut can also be used on non-array buttons, so was an issue for them as well.

To prevent the "copy-to-selected" behavior, refine the IS_ALLSELECT_EVENT macro to be more specific.

Pasting numerical array buttons happens with `Ctrl + Alt + V`. Holding `Alt` also triggers uiSelectContext, so having other nodes/ objects etc. selected while doing this would try to copy the pasted values back to other objects (possibly to the ones you pasted from) and that happens relative to the original value, so the value actually changes. NOTE: the `Ctrl + Alt + V` shortcut can also be used on non-array buttons, so was an issue for them as well. To prevent the "copy-to-selected" behavior, refine the `IS_ALLSELECT_EVENT` macro to be more specific.
Philipp Oeser added 1 commit 2023-05-25 13:55:14 +02:00
916d9018d4 Fix #108096: UI: copy-paste array buttons can change source properties
Pasting numerical array buttons happens with `Ctrl + Alt + V`.
Holding `Alt` also triggers uiSelectContext, so having other nodes/
objects etc. selected while doing this would try to copy the pasted
values back to other objects (possibly to the ones you pasted from) and
that happens relative to the original value, so the value actually
changes.

To prevent the "copy-to-selected" behavior, check for the specific button
combination in `ui_apply_but` and skip it in that case.
Philipp Oeser added this to the User Interface project 2023-05-25 13:55:22 +02:00
Philipp Oeser requested review from Harley Acheson 2023-05-25 13:55:33 +02:00
Philipp Oeser requested review from Julian Eisel 2023-05-25 13:55:43 +02:00
Philipp Oeser requested review from Campbell Barton 2023-05-25 13:55:51 +02:00
Member

This isn't just for arrays:

Paste1.gif

This isn't just for arrays: ![Paste1.gif](/attachments/734aa1cb-21ed-4b7d-9388-6ce6ebe32a5b)
Philipp Oeser changed title from Fix #108096: UI: copy-paste array buttons can change source properties to Fix #108096: UI: copy-paste buttons can change source properties 2023-05-26 08:48:00 +02:00
Author
Member

This isn't just for arrays:

Paste1.gif

With the same Ctrl + Alt + V shortcut you mean? Clarified the commit message in that regard.

> This isn't just for arrays: > > ![Paste1.gif](/attachments/734aa1cb-21ed-4b7d-9388-6ce6ebe32a5b) > With the same `Ctrl + Alt + V` shortcut you mean? Clarified the commit message in that regard.
Member

With the same Ctrl + Alt + V shortcut you mean?

Yes, the above was with the same ctl-alt-c and ctrl-alt-v process. In case is_array_paste should be reconsidered for variable name.

> With the same `Ctrl + Alt + V` shortcut you mean? Yes, the above was with the same ctl-alt-c and ctrl-alt-v process. In case `is_array_paste` should be reconsidered for variable name.
Author
Member

With the same Ctrl + Alt + V shortcut you mean?

Yes, the above was with the same ctl-alt-c and ctrl-alt-v process. In case is_array_paste should be reconsidered for variable name.

well the shortcut is meant for array pasting (see argument for ui_but_paste), so think it still makes sense

> > With the same `Ctrl + Alt + V` shortcut you mean? > > Yes, the above was with the same ctl-alt-c and ctrl-alt-v process. In case `is_array_paste` should be reconsidered for variable name. > > well the shortcut is meant for array pasting (see argument for `ui_but_paste`), so think it still makes sense

This fix feels too spesific, we could instead expand IS_ALLSELECT_EVENT so it only responds to events which are expected to be used for multi button editing.

e.g.

#  define IS_ALLSELECT_EVENT(event) \
    (((event)->modifier & KM_ALT) != 0 && \
     (ISMOUSE((event)->type) || ELEM((event)->type, EVT_RETKEY, EVT_PADENTER)))

(this can be made into a function too).


This way we don't need to pick out individual keys whenever this kind of conflict occurs.

This fix feels too spesific, we could instead expand `IS_ALLSELECT_EVENT` so it only responds to events which are expected to be used for multi button editing. e.g. ``` # define IS_ALLSELECT_EVENT(event) \ (((event)->modifier & KM_ALT) != 0 && \ (ISMOUSE((event)->type) || ELEM((event)->type, EVT_RETKEY, EVT_PADENTER))) ``` (this can be made into a function too). --- This way we don't need to pick out individual keys whenever this kind of conflict occurs.
Author
Member

This fix feels too spesific, we could instead expand IS_ALLSELECT_EVENT so it only responds to events which are expected to be used for multi button editing.

Sounds better indeed, thx for the heads up!
Will update the PR shortly

> This fix feels too spesific, we could instead expand `IS_ALLSELECT_EVENT` so it only responds to events which are expected to be used for multi button editing. > Sounds better indeed, thx for the heads up! Will update the PR shortly
Philipp Oeser added 1 commit 2023-06-01 15:17:32 +02:00
b27578b758 tweak event handling
make IS_ALLSELECT_EVENT more specific in regards to events which are
expected to be used for multi button editing (instead of checking the
events for array pasting specifically)
Campbell Barton reviewed 2023-06-06 15:39:14 +02:00
@ -277,3 +277,3 @@
const double value_orig);
# define IS_ALLSELECT_EVENT(event) (((event)->modifier & KM_ALT) != 0)
# define IS_ALLSELECT_EVENT(event) \

There should be an explanation for why only certain events are filtered (with a reference to #108096). Otherwise this seems fine.

There should be an explanation for why only certain events are filtered (with a reference to `#108096`). Otherwise this seems fine.
Campbell Barton approved these changes 2023-06-06 15:39:21 +02:00
Philipp Oeser added 1 commit 2023-06-07 11:12:06 +02:00
Philipp Oeser merged commit c51467cd4c into blender-v3.6-release 2023-06-07 11:19:10 +02:00
Philipp Oeser deleted branch 108096 2023-06-07 11:19:14 +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#108270
No description provided.