Selecting multiple channels in the transform window applies first value to all channels #116730

New Issue

Open

opened 2024-01-03 00:46:33 +01:00 by Peter-Conlin · 6 comments

Peter-Conlin commented

2024-01-03 00:46:33 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
The action of dragging-selecting vertically over multiple transform vector values will apply the first value to all of the selected values.

Exact steps for others to reproduce the error

Open blender.
Expand transform window (arrow).
Select default cube.
Move cube in X, Y, and Z to different values.
Press and hold on the X channel box.
Drag down to the Z channel box.
Release.

Outcome: all values will be a copy of whatever X was.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** The action of dragging-selecting vertically over multiple transform vector values will apply the first value to all of the selected values. **Exact steps for others to reproduce the error** 1. Open blender. 2. Expand transform window (arrow). 3. Select default cube. 4. Move cube in X, Y, and Z to different values. 5. Press and hold on the X channel box. 6. Drag down to the Z channel box. 7. Release. Outcome: all values will be a copy of whatever X was.

Peter-Conlin added the

labels 2024-01-03 00:46:34 +01:00

Iliya Katushenock added the

label 2024-01-03 00:48:36 +01:00

Pratik Borhade commented

2024-01-03 04:37:09 +01:00

Member

Hi, thanks for the report. AFAIK this is expected when editing multiple buttons (uiHandleButtonMulti), value of active button is copied to others when entered to edit them instead of dragging
For help using Blender, please try one of the community websites: https://www.blender.org/community/

If you think you found a bug, please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, and a .blend file with exact steps to reproduce the problem..

Hi, thanks for the report. AFAIK this is expected when editing multiple buttons (`uiHandleButtonMulti`), value of active button is copied to others when entered to edit them instead of dragging For help using Blender, please try one of the community websites: https://www.blender.org/community/ If you think you found a bug, please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, and a .blend file with exact steps to reproduce the problem..

Pratik Borhade closed this issue

2024-01-03 04:37:12 +01:00

Blender Bot added

and removed

labels 2024-01-03 04:37:13 +01:00

Peter-Conlin commented

2024-01-03 05:41:48 +01:00

Author

Hi Pratik,

Could you explain the use-case of this feature?

The only outcome I can see for it is to accidentally overwrite existing values with incorrect information. I can't think of a situation where it would be beneficial to have all three values of a vector become the same, without even inputting any change.

Now, if I were to paste a value in, that might make sense, but I would expect to be able to paste in a full vector.

incidentally I found this issue while trying to copy the full position vector. It seems like I will have to copy over all three values, one at a time. Are you sure this is the intended function?

Hi Pratik, Could you explain the use-case of this feature? The only outcome I can see for it is to accidentally overwrite existing values with incorrect information. I can't think of a situation where it would be beneficial to have all three values of a vector become the same, without even inputting any change. Now, if I were to paste a value in, that might make sense, but I would expect to be able to paste in a full vector. incidentally I found this issue while trying to copy the full position vector. It seems like I will have to copy over all three values, one at a time. Are you sure this is the intended function?

Peter-Conlin reopened this issue

2024-01-03 05:41:51 +01:00

Blender Bot added

and removed

labels 2024-01-03 05:41:53 +01:00

Pratik Borhade commented

2024-01-03 06:13:13 +01:00

Member

To copy entire vector, you can use ctrl alt c/v when mouse is over the properties: as mentioned in manual

The only outcome I can see for it is to accidentally overwrite existing values with incorrect information

Even if we don't tweak them when multi-buttons are selected, this will happen eventually when you send value from keyboard (i.e. all selected buttons will reflect the same values after pressing number key).

This is not a bug AFAIK. Rather a request to improve or change the existing behavior :)

To copy entire vector, you can use `ctrl alt c/v` when mouse is over the properties: [as mentioned in manual](https://docs.blender.org/manual/en/latest/interface/keymap/introduction.html#properties:~:text=Ctrl%2DAlt%2DC%20%E2%80%93%20Copy%20the%20entire,the%20entire%20vector%20or%20color%20of%20the%20field.) > The only outcome I can see for it is to accidentally overwrite existing values with incorrect information Even if we don't tweak them when multi-buttons are selected, this will happen eventually when you send value from keyboard (i.e. all selected buttons will reflect the same values after pressing number key). This is not a bug AFAIK. Rather a request to improve or change the existing behavior :)

Germano Cavalcante commented

2024-01-03 17:13:47 +01:00

Member

Hi @Peter-Conlin,

The behavior you described "to copy over all three values" instead repeat the value of the active button indeed seems more intuitive to handle this interaction, but is not considered a bug. (And it can even be confusing for some users)

The idea behind the current behavior is to copy the value of the active button and optionally wait for keyboard input (without Ctrl+C distinction). This can be useful when inputting values from the keyboard, as all selected buttons will reflect the same values.

It's worth noting that changes to the behavior of Blender's interface require careful consideration and discussion with the UI team to ensure they align with Blender's design principles and user expectations.

If you would like to propose a change or improvement to this behavior, I recommend submitting a feature request. You can do this by following the links: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

(Please keep in mind that users may have already become accustomed to the current design, so any changes should be carefully evaluated to balance the needs of different users).

I am closing this report as this bug tracker is only for bugs and errors.

Hi @Peter-Conlin, The behavior you described "to copy over all three values" instead repeat the value of the active button indeed seems more intuitive to handle this interaction, but is not considered a bug. (And it can even be confusing for some users) The idea behind the current behavior is to copy the value of the active button and optionally wait for keyboard input (without Ctrl+C distinction). This can be useful when inputting values from the keyboard, as all selected buttons will reflect the same values. It's worth noting that changes to the behavior of Blender's interface require careful consideration and discussion with the UI team to ensure they align with Blender's design principles and user expectations. If you would like to propose a change or improvement to this behavior, I recommend submitting a feature request. You can do this by following the links: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests (Please keep in mind that users may have already become accustomed to the current design, so any changes should be carefully evaluated to balance the needs of different users). I am closing this report as this bug tracker is only for bugs and errors.

Germano Cavalcante closed this issue

2024-01-03 17:13:51 +01:00

Blender Bot added

and removed

labels 2024-01-03 17:13:53 +01:00

Peter-Conlin commented

2024-01-03 20:37:35 +01:00

Author

Hi @Peter-Conlin,

The behavior you described "to copy over all three values" instead repeat the value of the active button indeed seems more intuitive to handle this interaction, but is not considered a bug. (And it can even be confusing for some users)

The idea behind the current behavior is to copy the value of the active button and optionally wait for keyboard input (without Ctrl+C distinction). This can be useful when inputting values from the keyboard, as all selected buttons will reflect the same values.

It's worth noting that changes to the behavior of Blender's interface require careful consideration and discussion with the UI team to ensure they align with Blender's design principles and user expectations.

If you would like to propose a change or improvement to this behavior, I recommend submitting a feature request. You can do this by following the links: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

(Please keep in mind that users may have already become accustomed to the current design, so any changes should be carefully evaluated to balance the needs of different users).

I am closing this report as this bug tracker is only for bugs and errors.

Hi Germano,

Perhaps we're dealing in different terms. 'Bug' seems to mean something different to you internally, while on the outside I can only see what the program is doing, vs what my expectation of it is.

If you have a clearly defined documentation of features that states that this is exactly how it should work, then by all means close this. But expect to continue to get similar reports, because I can't see that documentation, and can only report issues that fall out of scope of what I believe the software should be doing.

Perhaps you could do more to clearly define the avenues which users could use to report issues which are not a bug, but still need to be worked on?

For example: in the current build, you can go the the menu and find that 'Help>Report A Bug' is readily available, and the only option. Additionally I was unable to find any information that specifically defined what was considered a bug and what was not. I think we can both agree this is by design, and not a bug, and yet also, has caused both of us to expend unnecessary time and energy when there are better solutions that could be implemented.

Such as including a second option for 'User Feedback and Requests'. You might even put a disclaimer on the bug report page to confirm that the report is in fact a bug, defining what you mean by 'bug', and offering a redirect for users that misunderstood. This might not deflect every report to the correct location, but it might alleviate some in future.

> Hi @Peter-Conlin, > > The behavior you described "to copy over all three values" instead repeat the value of the active button indeed seems more intuitive to handle this interaction, but is not considered a bug. (And it can even be confusing for some users) > > The idea behind the current behavior is to copy the value of the active button and optionally wait for keyboard input (without Ctrl+C distinction). This can be useful when inputting values from the keyboard, as all selected buttons will reflect the same values. > > It's worth noting that changes to the behavior of Blender's interface require careful consideration and discussion with the UI team to ensure they align with Blender's design principles and user expectations. > > If you would like to propose a change or improvement to this behavior, I recommend submitting a feature request. You can do this by following the links: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > > (Please keep in mind that users may have already become accustomed to the current design, so any changes should be carefully evaluated to balance the needs of different users). > > I am closing this report as this bug tracker is only for bugs and errors. > Hi Germano, Perhaps we're dealing in different terms. 'Bug' seems to mean something different to you internally, while on the outside I can only see what the program is doing, vs what my expectation of it is. If you have a clearly defined documentation of features that states that _this_ is exactly how it should work, then by all means close this. But expect to continue to get similar reports, because I can't see that documentation, and can only report issues that fall out of scope of what I believe the software should be doing. Perhaps you could do more to clearly define the avenues which users could use to report issues which are not a bug, but still need to be worked on? For example: in the current build, you can go the the menu and find that 'Help>Report A Bug' is readily available, and the _only_ option. Additionally I was unable to find any information that specifically defined what was considered a bug and what was not. I think we can both agree this is by design, and not a bug, and yet also, has caused both of us to expend unnecessary time and energy when there are better solutions that could be implemented. Such as including a second option for 'User Feedback and Requests'. You might even put a disclaimer on the bug report page to confirm that the report is in fact a bug, defining what you mean by 'bug', and offering a redirect for users that misunderstood. This might not deflect every report to the correct location, but it might alleviate some in future.

Peter-Conlin reopened this issue

2024-01-03 20:37:38 +01:00

Blender Bot added

and removed

labels 2024-01-03 20:37:39 +01:00

Germano Cavalcante commented

2024-01-03 21:10:19 +01:00

Member

The code appears to have been analyzed by @PratikPB2123 who identified that the current behavior is in fact by design.

For what is considered "bug", you can visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

In fact the manual does not appear to be documenting this behavior.
However, we have another place for problems in the manual:
https://projects.blender.org/blender/blender-manual

But since there is a lack of documentation, I will set it as needing information from the developers.
Naturally, the responsible developer should also be notified, but in this case, as it is an old feature, there is no longer an active developer. Therefore, this report will remain in the issue task stack of the User Interface team, which will evaluate it further.

The code appears to have been analyzed by @PratikPB2123 who identified that the current behavior is in fact by design. For what is considered "bug", you can visit: https://wiki.blender.org/wiki/Reference/Not_a_bug In fact the manual does not appear to be documenting this behavior. However, we have another place for problems in the manual: https://projects.blender.org/blender/blender-manual But since there is a lack of documentation, I will set it as needing information from the developers. Naturally, the responsible developer should also be notified, but in this case, as it is an old feature, there is no longer an active developer. Therefore, this report will remain in the issue task stack of the `User Interface` team, which will evaluate it further.

Germano Cavalcante added

Needs Info from Developers

and removed

labels 2024-01-03 21:10:35 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

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#116730

No description provided.