I agree w/ Midnight, I've been thinking of the same thing and have been facing the same problem.
In response to your concern, Skurj, he can leave the default settings the way they are, but just providing optional map points for Activate and Deactive primitives for some of the toggled stuff would be great.
Eg, for gear mapping there could be:
Gear Toggle (this is same as we have now) - Default G
Gear up - Default unmapped
Gear down - Default unmapped
The above changes could be done pretty quickly if the code isn't too hacked together for gear events and stuff.
A more complicated enhancement I would like to suggest would be providing an interface for getting various data points via UDP. This way, someone could write an interface to output the data to whatever hardware we wanted.
For instance, provide the following data:
primary_gun could be a bool or single byte value that says the main gun is firing.
secondary_gun could be the same for the secondary gun.
engine_running could be same for whether the engine is on
ias_value could be a word w/ a numeric representation of the indicated airspeed
gs_value could be the absolute speed
fuel_one
fuel_two
fuel_three
fuel_four (etc) could indicate percentage of fuel remaining in each tank
These and various other data points could help some of the more hardcore simmers have AH reporting data to instruments in their cockpits, like what X-Plane does.
I don't know if there would be a huge demand for this, but it would make for some pretty kicking demonstration cockpits at conventions.