Maniphest T64517

Old and standard behavior gone from navigation while Gizmo's active.
Closed, Resolved

Assigned To
Campbell Barton (campbellbarton)
Authored By
Ajlan Altug (jacobo)
May 12 2019, 5:03 PM
Tags
  • BF Blender
Subscribers
Ajlan Altug (jacobo)
Alex (SpectreFirst)
Campbell Barton (campbellbarton)
William Reynish (billreynish)

Description

bSystem Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.94

Blender Version
Broken: version: 2.80 (sub 61), branch: blender2.7, commit date: 2019-05-10 22:48, hash: rBb1af68200159
Worked: (optional)

Please watch the video that demonstrates the problem. Thank you.

Related Objects

Mentioned Here
rB27d097e92d54: Python API: expose conversion between tweaked NLA strip and scene time.

Event Timeline

Ajlan Altug (jacobo) created this task.May 12 2019, 5:03 PM
William Reynish (billreynish) assigned this task to Campbell Barton (campbellbarton).May 12 2019, 10:09 PM
William Reynish (billreynish) lowered the priority of this task from 90 to 50.
William Reynish (billreynish) added subscribers: Campbell Barton (campbellbarton), William Reynish (billreynish).

You should probably clarify that you are not using the default keymap - at least I am guessing you are not, because by default this is not a problem.

It *is* an issue if you use Maya-style Alt-dragging for the viewport, because the gizmos are invoked with any modifier key pressed.

@Campbell Barton (campbellbarton) Not sure where to set this but I am guessing it should be a relatively easy fix?

William Reynish (billreynish) changed the task status from Duplicate to Resolved.May 12 2019, 10:58 PM
Ajlan Altug (jacobo) added a comment.May 13 2019, 12:22 AM

Sorry I forgot to point that out but yes, you nailed it; I am using a different navigation keymap other than the default, and yeah it's an Alt driven navigation keymap. Since the previous version of Blender could do this without a hitch, I take it that it's successor could do it as well. May I ask why it's been labeled as "Resolved" tho? Does this mean that it will be fixed in a coming daily build?

Thank you;

AJ

William Reynish (billreynish) added a comment.May 13 2019, 12:41 AM

If you use your own keymap you may need to fix it there yourself. But if you use either of the built-in keymaps, it should work correctly now.

The Industry Compatible keymap is Alt-driven and now works correctly.

Ajlan Altug (jacobo) added a comment.May 13 2019, 1:19 AM

snip"If you use your own keymap you may need to fix it there yourself"snip

I'm sorry but I really don't know how. Could you elaborate?

Thank you;

AJ

Ajlan Altug (jacobo) added a comment.May 13 2019, 1:26 AM

And btw, I switched to the "Industry Compatible" keymap mode just now and the issue still persists in the latest build.

AJ

Ajlan Altug (jacobo) added a comment.EditedMay 14 2019, 12:39 AM

Ok I dowloaded 2.8 version 27d097e92d54 and the "industry standard" preset works. But I want to know how a preset could make this work and a manual assignment won't, where a preset is, uh... A preset, as the word implies. A table of preset values that are set by the user to alter a list of parameters... I checked and all the navigation and transform shortcuts under that preset are completely identical to their counterparts under mine. So what gives?

William Reynish (billreynish) added a comment.May 16 2019, 10:04 AM

Currently you must set the transform gizmo to not react to Any modifier key.

Alex (SpectreFirst) added a subscriber: Alex (SpectreFirst).May 16 2019, 11:19 AM

If I'm not mistaken, disabling "Any" in this field should do the trick. For some reason I can't find it manually so I'm just using search function by Gizmo