OK, I think my shake-down tests have uncovered most of the obvious bugs. I think I'm ready for some other testers.
Here's a link (
oolite_keyconfig.zip) to a ZIP that contains the following:
1. oolite.exe - a 64bit version of Oolite 1.91
2. descriptions.plist
3. keyconfig2.plist
4. missiontext.plist
5. verifyOXP.plist
You need to have a copy of the latest Trunk available to make this work. Rename the current exe file (to, say, "oolite.exe.bak"), then drop the new exe into the folder. Do the same with the plist files in the "Config" folder. And then...fingers crossed...keyboard configuration should be available from the front menu, and also during play (docked and when paused in flight). Mouse control should work as well.
This is extremely experimental, so don't be surprised if things go pear-shaped. But there are a couple of things I'd like to get tested.
1. Performance. Do you notice any lag or delay when pressing keys, particular during large battles, etc.
2. Flexibility. Can you enter and use all the keys on your keyboard, including Ctrl/Alt variations? Particular important if you're using a non-QWERTY US/UK keyboard).
3. Accuracy. Are conflicts being correctly identified? Is everything getting saved/restored successfully?
4. Clarity. Did you find anything confusing to use or understand? Did something happen you didn't expect, or something not work in the way you expected?
Let me know what you find. If a Linux or Mac person who can build from source wants to give this a try, the
new_keyconfig branch has my latest check-in, so you could try building it yourself. I'd be very interested to hear the results.