mavlink / qgroundcontrol

Cross-platform ground control station for drones (Android, iOS, Mac OS, Linux, Windows)
http://qgroundcontrol.io
3.26k stars 3.59k forks source link

Planning: offer to apply "mission start" altitude to all mission items. #6493

Open AndKe opened 6 years ago

AndKe commented 6 years ago

If user change "Waypoint Alt" - then he is offered to apply it to all waypoints.

screenshot from 2018-05-23 23-45-11

Antiheavy commented 6 years ago

This seems like a useful idea. Another method might be some sort of “select all” feature where altitude and speed can then be globally set to all waypoints with some important exceptions such as Land waypoints.

DonLakeFlyer commented 6 years ago

I'm not convinced since the concept of what you are doing is kind of different. Waypoints all have altitudes in them. The tendency to set a mission all a the same altitude is common. Hence changing all the altitudes at once make sense to be able to adjust. But if you specifically change flight speed at various points in a mission. Then if you are adding specific new commands to the mission to change speed. If you don't want to do that anymore then it would make more sense to remove them. Otherwise you are just leaving a pile of flight speed change commands in the mission which turns into noops. That seems strange to me.

AndKe commented 6 years ago

@DonLakeFlyer I understand your view perfectly :) I did not explain my use: What actually was the case, was a stereocam flight about 20 waypoints, at different speed/altitude. It's easier to modify all to 5m/s , then half of them to 6m/s , than to modify all from 3m/s to 4m/s and 4m/s to 5m/s. -half the job :)

Which bring me to the minor-programming request. (not just code reuse like this was)