Subscribe to all messages

[IhsenBouallegue]

Subscribe to all messages

[IhsenBouallegue]

ping @wucke13

[wucke13]

Hey, we can add a second method that subscribes all. Would you fancy preparing a PR for that?

[IhsenBouallegue]

I would be more than happy to implement it, but I would love some pointers and tips as I am new to all of this. That way it doesn't get frustrating and then give up halfway. Let me know what steps I need to take/how the interface should look like. Stuff like pseudo code and/or pointers to certain files that need to be adjusted would be helpful.

[IhsenBouallegue]

@wucke13 any ideas?

[IhsenBouallegue]

Sadly this project seems abandoned, what a shame 😢

[wucke13]

I don't feel no shame 😄
So, to implement this I see three options:

1. one either has to name every variant of the MavMessage enum for a message set, and subscribe to it. This is extremely tedious.
2. alter the source code of the original mavlink crate to include an iterator over all variants of said MavMessage enum. That way one does not have to type all the combinations, instead one can benefit from code generation already included in bespoke crate.
3. Just go through the integer IDs for the subscribing, ignoring errors for unknown IDs.

I would definitely rule out option 1. Option 2. seems to be the technically best solution, but back when I pursued an active interest in this it seemed almost impossible to agree on something with the mavlink maintainers, probably like me they were and/or are short on time. Option three is the quick'n dirty approach.