Multiple device support

[nicola02nb]

Changes made

Added multiple device support with command arg -d, --device INDEX
Actions can be executed only to one device at a time

Checklist

• I adjusted the README (if needed)
• For new features in HeadsetControl: I discussed it beforehand in Issues or Discussions and adhered to the wiki

[Sapd]

Thank you!

Some points for now:

• --test-device seems to be completely broken
  • In the end I think it would be nice that also the test device is shown as another device (when the parameter is provided) together with a real device when one its connected
• -d should be I think a bit more flexible. It should also support -d vendorid:deviceid (like in the --dev menu). However I like the approach with showing the indexes directly in the text when running the program

[nicola02nb]

• --test-device seems to be completely broken

Ok, didn't checked that...

• In the end I think it would be nice that also the test device is shown as another device (when the parameter is provided) together with a real device when one its connected

You mean to add it to the curernt list of connected devices?

• -d should be I think a bit more flexible. It should also support -d vendorid:deviceid (like in the --dev menu). However I like the approach with showing the indexes directly in the text when running the program

Maybe an hybrid solution where you can use both of them would be also better...

Question: Which interface I choose to interact with a device changes nothing, right?

[Sapd]

Maybe an hybrid solution where you can use both of them would be also better...

Yes thats what I mean. That both -d index and -d vendorid:deviceid works. There is already a function for that, it just has to be moved to utility.c and modified in a way that also one id works:

HeadsetControl/src/dev.c

Line 72 in 689c1fc

static int get_two_ids(char* input, int* id1, int* id2)

You mean to add it to the curernt list of connected devices?

Yes, when the parameter is provided.

Question: Which interface I choose to interact with a device changes nothing, right?

Basically there is no sense in choosing the interface, its already given by the device implementation

[nicola02nb]

Running tests locally gives no errors.
I'm wonderig why CI does...

[nicola02nb]

Now it should be all done

it just has to be moved to utility.c and modified in a way that also one id works

Missed that...