When RMB is pressed to look around, LMB and MMB still trigger hotspots, unlike in the "Look by mouse" mode. this causes the RMB+MMB camera-dragging to be error-prone, making the user having to watch out for any notspots underneath the cursor before dragging the view.
I thought I'd fixed this so in RMB-look, no hotspots would trigger. Hmmmmmm.
Can you check if it's fixed on next, maybe? But, I thought I did back-port it already.
Checked, the code I expect to block this when RMB-look is active, exists on next and 2020.3. So maybe we're not talking about the same thing?
As far as I remember there used to be a problem with it picking up hotspots on the way -- and if this was that case, that's been fixed. The problem now only appears if the pressed state of LMB or MMB starts while both RMB is pressed and the cursor is over a hotspot.
I will check naxt tonight. But as far as I know the problem exists on both versions.
Ahhh, I see. So it's about new button changes while RMB is active. I thougth I handled that case but maybe I forgot it. Function isRightDragLookActive() in mouseinput.cxx should help you :)
Correction: only LMB triggers hotspots while RMB is pressed
Oops, no, not really, MMB too.
Affects both 2020.x and Next (at least)
Last edit: Anonymous 2022-02-18