Page MenuHome

Zooming with MacBook Pro trackpad zooms to random location
Open, Waiting for Developer to ReproducePublic

Description

System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-09 22:31, hash: rBf61a8a2abd07
Worked: (optional)

Short description of error
Only on the Shader Editor.
When you zoom in using the MacBook trackpad it zooms randomly, not following the cursor. This is different than the behaviour on the 3D Viewport.

Exact steps for others to reproduce the error
Zoom in on the Shader Editor. It zooms differently than the 3D Viewport, which zooms to the mouse cursor location.

Details

Type
Bug

Event Timeline

William Reynish (billreynish) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Oct 11 2019, 9:27 PM

Are you using factory defaults? By default it doesn't zoom to the mouse cursor.

Yup. But I believe it should zoom to the mouse cursor, as it’s the way it behaves on the viewport. Trackpad pinch to zoom is inconsistent between the shader editor and viewport...

No that’s not how it works by default. It zooms to the center.

Oh I'm sorry for the confusion! There really is a toggle for that. Is there a way to port the behaviour to the shader editor as well, then? Because it's behaving differently even with the toggle turned on...

If it doesn't port the behaviour from the viewport couldn't it be considered a bug? It would help my workflow so much if this got fixed...

Philipp Oeser (lichtwerk) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Fri, Nov 22, 12:40 PM

If it doesn't port the behaviour from the viewport couldn't it be considered a bug?

I would say so,
Afaict, this Preference is also used in VIEW2D zooming.

@William Reynish (billreynish) : is this working for you in the Shader Editor?

the fix for that is waiting for a code revision: D5076 . @William Reynish (billreynish) can you give it a look?