mode change corrupts plane setup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Select MODE1
2. Create and set up a model as if to fly in mode 1
3. Switch to MODE2

What is the expected output? What do you see instead?
expect: Someone with flying skills for mode 2 could fly the plane.
real: everything is mixed up, some functions are swapped, some are okay.

What version of the product are you using? On what operating system?
R155

Please provide any additional information below.
I expected that when changing the mode, the stick functions would swap, and the 
rest would remain the same. But in the firmware there are apparently also 
functions that bypass the mode function, and directly read the sticks. I found 
this out when I sold a plane (I fly mode 1, the other guy mode 2), and copied 
the EEPROM in the other 9x with same R155 firmware.
In the end, I erased the eeprom, and started blank.

Original issue reported on code.google.com by harm.del...@echostar.com on 3 Jan 2011 at 8:09

[GoogleCodeExporter]

you requested behaviour is not implemented.
In the current implementation the mode change only renames the input channel 
names.
It changes (nearly no) functionality. Only exception: THR-Warning, THR-Timer.
This means that it is not possible to change the mode after the mixers are 
programmed,
you have to setup the mode first and then program the mixers and expos.
This saves a little bit of cpu-time during mixer calculation.
Meanwhile i think it would be no cpu-time problem to implement this feature.

Original comment by th...@t-online.de on 9 Jan 2011 at 12:12

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

feature is now implemented, but not yet released.

Original comment by th...@t-online.de on 11 Jan 2011 at 11:18

• Changed state: Started

[GoogleCodeExporter]

Original comment by th...@t-online.de on 27 Jan 2011 at 12:00

• Changed state: Done