It'd also be great if they added Hold/Toggle options for each on/off control (or else added a direct binding for it).
Yes I forgot about that. Between not being able to hold/toggle every control and only being able to add two inputs per control I've had to jump through a bunch of TARGET/FreePIE/vJoy hoops to get things close to the way I want.
I believe it does not inform you when you use an already bound key too, which makes it tiresome to keep in order.
A message appears at the bottom of the screen very briefly; very easy to miss. When I catch a glimpse of it I usually just cancel out of editing rather than try to figure out which control I just broke.
Live and Beta sharing key-bindings isn't ideal either. It's great that when you launch the Beta, it already has your controls from Live set. But if you're tinkering around with your controls in Beta, you don't necessarily want to mess up your controls in Live.
As a rule, live and test environments should be completely separated. Here again, though, things aren't as bad as they used to be. You'll remember that the 1.2 beta added new keybinds which people duly configured. Then when they went back to live the new binds caused the client to reject the whole configuration. Now the bindings files include a version number and the client knows to ignore any versions it doesn't recognise.
If you're playing the 1.5 or 2.0 beta right now you may well find you have
Custom.binds,
Custom.0.8.binds and
Custom.1.8.binds in your configuration directory. The first is obsolete and would be read only if the others didn't exist. The 0.8 file is the 1.4+ format and is used by the live client. The 1.8 file is the format used by the beta.
If you edit your bindings with a client which supports a particular version it will save the changes to the appropriate file even if an older one was initially read.
Yes, its poor but I don't see it as a priority though. Can't say as I go into it much after getting things set up
You're going to have a lot of fun when Horizons launches.