The most infuriating feature of Resolve

The most infuriating feature in Resolve.... don't get me wrong, I LOVE the program....but this one takes the cake. I'm on a clip moving a parameter...then I go to move a second parameter but Resolve has already moved itself to another clip. What?! I did't go to another clip, I'm still on the same clip but Resolve decides to highlight another one. This is crazy. Am I missing something, am I doing something wrong?...who could've possibly thought this was a good program behavior?. Help!

Any chance you have a control surface like the Speed Editor that you might be bumping? I've had this happen a few times while reaching over my SE and grazing the shuttle.

It does sound like you are doing something wrong. Maybe post a link to a screen capture demonstrating the issue, as I have never seen this problem in 20 years of using Resolve!

I'll take your word for it and fiddle around. thanks

Maybe this helps: if you ever had a MIDI console connected for use in Fairlight and taken it off, switch it off in the preferences too then! I experienced this when still under beta in 17 and tried to hunt it down as a bug (with a lot of help by BM's Rohit).
My audio faders were changing settings or jumping about and I didn't understand why. In my case, it was a friend, a guy very good at sound sweetening, who had used his console for a session on my project but took it with him later.

Thank you, Uli... I don't have a controller but I'll check my preferences and see if I can shut it off.

Are you by any chance typing in values to the parameters and think you're going from one field to another with arrow keys or Tab or something like that? You may be using keyboard shortcuts to go to the next clip.

Also, there is a bug currently where if you are using up/down arrow to increment/decrement a parameter and it is an integer parameter, you get one change and then it leaves the field and the next up/down arrow will move you to previous or next clip.

(When I say "integer" I literally mean an integer field: no period in it at all. For example, a count field. If it has a decimal point in it, even if it's only "0" after the decimal point, that's not an integer field.)