Closed ddd999 closed 7 months ago
Converting to draft because I realized it's going to be mandatory to have a way to select the network interface and therefore, which URI gets sent in the VIDEO_STREAM_INFORMATION message. The only way to send multiple URIs would be to send multiple messages (i.e., one to every interface), which seems kludgy.
This would work fine if the URI was hardcoded to one interface (or all interfaces), but there are plenty of use cases where a user would want to choose.
Nice! When you're ready, happy to give it test and review.
@stephendade, please review when you have time. Thank you!
Thanks to @TyIsI for helping with tips to get this working as well.
Great! Looks like you'll need a rebase first, as some of my recent tlogging changes aren't in here.
@stephendade I had a bit of fight with git but I believe it is all up to date now.
Yes, that look up to date now. I should have some time in the next few days to review.
Thanks for the review. I fixed the whitespace issues in mavManager.js and confirmed it didn't give any warnings with npm run lint. Added your suggestion for the Video page layout also--appreciate that input as I wasn't sure how to integrate the new option.
Looks good! Merging...
Addresses feature request issue #169
Enables Rpanion to respond to send COMMAND_ACK and VIDEO_STREAM_INFORMATION messages via MavLink in response to a MAV_CMD_REQUEST_MESSAGE.