Also, show CH# (e.g. CH7) rather than just the bare number in the
combobox, makes it more obvious that you're selecting an actual
channel number rather than an AUX channel number.
Since in RX_NONE bit is undefined, bit_check() will always return
true. Fix is just removing RX_NONE from the available RX types
on versions using feature bits for RX, since they won't allow
not having a RX configured (FC will fall back to RX_PPM).
Fixes#287
Chrome disallows synchronous URL loading, so all functions requiring
the JSON definitions for the settings over MSPv2 need to be async.
This required rewriting MSPHelper._getSetting() and all its callers
using promises.
Fixes#284
runSequence will return immediately, so tasks depending on
dist might fail the first time they're run. By explicitely passing
the callback, gulp will wait until runSequence runs both clean
and dist-build until it considers dist finished.
- Add a json file with the types of all settings, generated by
the settings generator on INAV.
- Implement MSPV2_SETTING and MSPV2_SET_SETTING, which gives us
access to any value exposed via settings.
- Use this to set small_angle to 180 in FW presets.
* Properly hiding/showing relevant controls for Minimum Failsafe Distance according to version (>= 1.7.4)
* Fixing bad maximum for centimeters distance
Had not realized developer branch was version 1.7.4; I had started this PR on master which which was on 1.7.3. Which explains my initial confusion about what to put here.
Add support for alarms that require unit conversion and non-integer
steps.
Implement support for the aforementioned alarms by using unit
conversion to display them in more convenient units when the OSD
is set to display imperial units.
Define an array of the available alarms. Display just the ones
understood by the FC.
Move alarm names and their help (if any) to the translatable
messages.
I believe everything works and is OK, but I am unclear about MSP/FC/Configurator versioning, so some of what I've done here may not be correct, or may need to be done differently. I would appreciate guidance/explanation.
It needs some spacing/comments cleanup I think,
and I need some guidance about version limiting its display. I don't know what the next version is, etc.