Background Image Transform Widget does NOT respect LOCKED transform channels #78771

New Issue

Adam Janz · 2020-07-09T19:25:48+02:00

Adam Janz commented

2020-07-09 19:25:48 +02:00

System Information
Operating system: Windows-8.1-6.3.9600-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Worked: (Unknown)

Short description of error
Hi Blender Dev Team, I've encountered a fairly troublesome bug while working with architectural blueprints as background images. The yellow transform widget that appears when hovering over a background or reference image can be manipulated even when the image's location, rotation, and scale is LOCKED in the item transform tab.

Moreover, setting keyframes for LocRotScale as well as for the Image Empty's "Size" property, cannot protect against the image being accidentally moved, only against being resized. This is due to the yellow transform widget keeping the image's origin stationary while applying the transformation. This bug results in extremely dangerous and unpredictable behavior, since crucial reference images can now be incorrectly scaled or re-positioned without warning.

(As a side note, the size property in the Object Data Properties tab seems to not update after scaling the yellow widget until AFTER you click on something else and then back on the image again either in the 3D viewport or in the Outliner... but that small issue with the dependency graph is not really a problem, just unusual.)

Exact steps for others to reproduce the error

Open a new .blend file.
Add > Image > Background (choose your image)
Lock ALL channels for Location, Rotation, and Scale
Set Keyframe for LocRotScale
Attempt to resize and move image using yellow corner widget
Notice image incorrectly resizes and moves, despite having channels LOCKED AND LocRotScale keyframes set
In the Object Data Properties tab, set a keyframe on the "Size" property.
Resize and move the image as before, using the yellow widget
Notice the image will resize to the size it was before when changing frame position (respecting the "Size" keyframe you set), but the location is NOT preserved (despite transform channels being locked and LocRotScale keyframes set).

Thanks so much for looking into this. I would also grateful to know if there is a way to disable the yellow corner widget as a temporary solution to avoid any accidental resizing.

Best regards,
Adam Janz

**System Information** Operating system: Windows-8.1-6.3.9600-SP0 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Worked: (Unknown) **Short description of error** Hi Blender Dev Team, I've encountered a fairly troublesome bug while working with architectural blueprints as background images. The yellow transform widget that appears when hovering over a background or reference image can be manipulated **even when the image's location, rotation, and scale is LOCKED** in the item transform tab. Moreover, setting keyframes for LocRotScale as well as for the Image Empty's "Size" property, **cannot protect** against the image being accidentally moved, only against being resized. This is due to the yellow transform widget keeping the image's origin **stationary** while applying the transformation. This bug results in extremely dangerous and unpredictable behavior, since crucial reference images can now be incorrectly scaled or re-positioned without warning. (As a side note, the size property in the Object Data Properties tab seems to not update after scaling the yellow widget until AFTER you click on something else and then back on the image again either in the 3D viewport or in the Outliner... but that small issue with the dependency graph is not really a problem, just unusual.) **Exact steps for others to reproduce the error** 1. Open a new .blend file. 2. Add > Image > Background (choose your image) 3. Lock ALL channels for Location, Rotation, and Scale 4. Set Keyframe for LocRotScale 5. Attempt to resize and move image using yellow corner widget 6. **Notice image incorrectly resizes and moves, despite having channels LOCKED AND LocRotScale keyframes set** 7. In the Object Data Properties tab, set a keyframe on the "Size" property. 8. Resize and move the image as before, using the yellow widget 9. **Notice the image will resize to the size it was before when changing frame position (respecting the "Size" keyframe you set), but the location is NOT preserved (despite transform channels being locked and LocRotScale keyframes set).** Thanks so much for looking into this. I would also grateful to know if there is a way to disable the yellow corner widget as a temporary solution to avoid any accidental resizing. Best regards, Adam Janz

Adam Janz commented

2020-07-09 19:25:48 +02:00

Added subscriber: @AdamJanz

Adam Janz commented

2020-07-09 19:53:16 +02:00

I thank the Lord Jesus Christ for showing me a temporary workaround:

Deselect "Active Object" under the "Viewport Gizmos" options. That will at least prevent someone from accidentally moving or resizing their reference image while its transform channels are locked, and is a viable workaround while we await a fix from the devs. Thanks and have a good day everyone.

Adam

I thank the Lord Jesus Christ for showing me a temporary workaround: **Deselect "Active Object"** under the "Viewport Gizmos" options. That will at least prevent someone from accidentally moving or resizing their reference image while its transform channels are locked, and is a viable workaround while we await a fix from the devs. Thanks and have a good day everyone. - Adam

Germano Cavalcante commented

2020-07-09 19:59:34 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-07-09 19:59:34 +02:00

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

Germano Cavalcante closed this issue

2020-07-09 19:59:34 +02:00

Germano Cavalcante self-assigned this 2020-07-09 19:59:34 +02:00

Germano Cavalcante commented

2020-07-09 19:59:34 +02:00

You can disable the image gizmo:

The image gizmo does not affect the object transform values. It represents other properties.

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

You can disable the image gizmo: ![image.png](https://archive.blender.org/developer/F8681363/image.png) The image gizmo does not affect the object transform values. It represents other properties. 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

Adam Janz commented

2020-07-09 20:20:43 +02:00

Thanks so much Germano for that info. I had not seen that checkbox before, so that's very helpful. Yes, I guess I could add this in the feature requests. However, since the image gizmo does not "technically" affect the object transform values, but the end result of using it DOES affect the object's perceived transform, such contradictory behavior would normally be considered a bug to most users. However, I'm glad there is more than one workaround to disable it from getting in the way. Thanks again for your help!

Thanks so much Germano for that info. I had not seen that checkbox before, so that's very helpful. Yes, I guess I could add this in the feature requests. However, since the image gizmo does not "technically" affect the object transform values, but the end result of using it DOES affect the object's **perceived transform**, such contradictory behavior would normally be considered a bug to most users. However, I'm glad there is more than one workaround to disable it from getting in the way. Thanks again for your help!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Background Image Transform Widget does NOT respect LOCKED transform channels #78771