Page MenuHome

Breakdowner remembers last Limit to Transform/Property Set
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87

Blender Version
Broken: since 2.80,
Worked: 2.79 and older

Short description of error
When using the breakdowner if you select any type of transform and axis, next time you use it it will remember those settings, which is confusing.

Exact steps for others to reproduce the error

  1. Create a bone.
  2. Enter Pose mode.
  3. Create 2 diffent keyframes.
  4. Shift the playhead on the timeline to a frame between the two.
  5. Ctrl+E in the viewport.
  6. Use G R S B or C to lock to a transform or property.
  7. Left click to confirm the operation.
  8. Press Ctrl+E again.

Expected result: lock to transform/property cleared
Actual result: the tool is remembering what you used last

So either of 2 options should work: or it doesn't remember at all (how it used to be in 2.79) or it only remembers if you're using the exact same control again but if you change controls it should refresh still.

Event Timeline

Alaska (Alaska) changed the task status from Needs Triage to Confirmed.May 18 2020, 10:22 AM
Alaska (Alaska) updated the task description. (Show Details)
Alaska (Alaska) added a subscriber: Alaska (Alaska).

I can confirm this happens.

This mode uses the region-relative mouse location, while this could be changed, it's working as intended.

This would make more sense as a design task - to change the operator to use relative mouse location since thats how all other transform operators work.

@Campbell Barton (campbellbarton) no i think you are talking about something different,

if you grab an object with g and then constrain it to X then accept the operation and then grab it again grabbing doesn't remember you were locking it to X, this is exactly what's happening with the breakdowner.

It's not intended and wasn't designed like this, because I proposed the locking to different transforms and axes and it worked fine up to and including 2.79, and at some point was changed in 2.8

Thank you Campbell! I cant believe my eyes,!