Move channel_override examples out of simple_goto and small_demo about dronekit-python HOT 7 CLOSED

Pull #124 will fix the small_demo.py case. I have left the RC override stuff there, but it is very clearly marked as "do not use".

from dronekit-python.

It appears that simple_goto no longer includes RC code.

Should we still split out RC code from vehicle_state? I would be in favor. It seems like it's an "advanced" topic and we want to not encourage that in the basic example, no matter how many warnings are attached.

from dronekit-python.

@tcr3dr I thought about this a lot and decided that it is more associated with vehicle state than anything else, and that creating an extra "advanced use" example to support this would actually highlight it more than I wanted. I do see your argument though - if you feel strongly add a final confirmation and I'll create another very simple example for "setting rc overrides". Otherwise just close this.

from dronekit-python.

I'd like to propose separating this then. Considering some of the long-term goals of maintaining abstractions over MAVLink and RC input, and since vehicle_state.py will eventually accumulate more features we want to highlight (and are more important), moving out "advanced" features gives us that level of flexibility. But this is totally low-priority.

from dronekit-python.

@tcr3dr OK. I am leaning this way too.

from dronekit-python.

I believe this is done.

from dronekit-python.

Yes, this was done ages ago :-)

from dronekit-python.