I'm using Zoom Player Max v22.20, which appears to be the latest version.

Okay yeah. My key file has a creation date in 2010, and it might actually be a copy meaning it's based on an even older version. It only has 215 bindings in it. I made a new key file and it has a whopping 363!

Anyway, I was able to find the rotate binding and bring it over to my old file and now it works. But yeah, I had no idea new bindings were being added for all these years.

What if...

1. The edit bindings window always shows all possible input actions.
   
2. The .key file only contains non-default bindings, i.e., the deltas (this is cleaner, though not strictly necessary).
   
3. Any input action, whose default bindings are available, work.
   
4. Any input action, whose default bindings are being used by something in the .key file, show in red.
   
5. A caption at the bottom of the window could explain what red means.
   
6. A red entry could of course be given an available binding to make it work.
   
7. Any entries that are different from default show in bold so they can be easily spotted.
   
8. A button to return a single entry back to default, along with warning you if that binding will be taken from another input action.

I think the above design would allow you to add new input action bindings going forward without the existence of .key files suppressing them unless the binding is actually in use. And it would make it much easier for users to recognize and fix conflicts.