Deprecate MAV_DATA_STREAM #266
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I know this is coming from upstream - but it's a bit weird, really. Know that I don't like data streams, but from a practical perspective, all GCSs use them and they'yre much easier to deal with on the autopilot that message intervals. I still think they should die, but I'm not sure we know how to kill them yet, at least on the ArduPilot side of things.... |
|
This does not kill them, this just signals the users that it will get killed at some point. |
|
we can't deprecate streams until we had a valid replacement |
|
Grouping of new (non discoverable) messages is not possible with SET_MEASSAGE_INTERVAL so this can not be deprecated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.