Copter: stop Follow mode being a subclass of Guided #31412
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refactoring over the years means it no longer needs any functionality that Guided once gave it.
I have copied in a few methods to retain existing behaviour, but I think we should consider changing some of these.
... e.g. I don't believe terrain failsafe is relevant as this is a velocity controller now.
... e.g. I don't think we want all of the behaviour that
is_guided_mode()returning true suggests... e.g. should we even allow takeoff in follow mode?!