@ben No, whatever the issue is now, it’s much harder to pin down / re-create than before. I had it happen semi-regularly on a media server that I have running at a TV studio, but they’re on hiatus right now so I can’t try it out there.
The only real clue I have is that it seems to coincide with whenever a perform window gets stuck to my cursor after attempting to drag said window by it’s titlebar. I regularly have a couple TD processes running, sometimes with multiple perform / network editor windows open (I know I know bad practice - sue me) and occasionally I beleive TD “misses” the “mouseUp” trigger when I’m done dragging and thus the perform (or sometimes network editor) window will continue following the mouse cursor even when the mouse button is released.
I’ve gotten very used to giving the mouse a little wiggle after every window move just to see if it’s free and if not, a couple clicks later it will let go. That’s always happened for as long as I’ve used TD… But recently sometimes after that, if the immediate next action is to attempt to use MMB (or even your mac friendly “holding down LMB” method :–) the value ladder will not pop up - almost as if the window is not in focus, or maybe TD is not expecting two “mouseDown” triggers in a row from the mouse. Clicking on the Windows desktop (often just with LMB, sometimes you actually have to click with MMB) and then clicking back into TD will often fix it.
Despite that, occasionally at the tv studio this would not fix it and I had to restart that TD process, but I can’t say why until I have access to test on that computer again (not through AnyDesk)
TLDR: Honestly this is not nearly as much of a nuisance as the previous version of this bug, and it’s probably related to having (at least for me) too many TD windows open and TD “missing” the ‘mouseUp’ message coming from the mouse. It’s almost always fixed by taking the TD window in question out of, and back into focus. AKA don’t lose sleep over it.