Allowing multiple hid connections at a time would solve multiple pain points. Mainly, when the hid slot is taken, we still advertise for dongle (nus). Unfortunately, the host devices don't care whether we advertise nus or hid - once a paired ble device is seen, they try to connect. This results into ugly reconnection loops and other headaches.
Ideally I would like the c2usb to allow multiphe hid connections and and provide an api which would allows us to control where the hid reports are routed to.
The way I understand it, this would mean extract state from the c2usb hogp code so that it can be kept in one structure that can be swapped under c2usb. We can own the state if it makes things easier. (E.g., numLockEtc states are already managed in the firmware because of multiple dongle operations. Not sure how much other state hogp actually needs.)
@benedekkupper can you elaborate on its feasibility and difficulty?
Allowing multiple hid connections at a time would solve multiple pain points. Mainly, when the hid slot is taken, we still advertise for dongle (nus). Unfortunately, the host devices don't care whether we advertise nus or hid - once a paired ble device is seen, they try to connect. This results into ugly reconnection loops and other headaches.
Ideally I would like the c2usb to allow multiphe hid connections and and provide an api which would allows us to control where the hid reports are routed to.
The way I understand it, this would mean extract state from the c2usb hogp code so that it can be kept in one structure that can be swapped under c2usb. We can own the state if it makes things easier. (E.g., numLockEtc states are already managed in the firmware because of multiple dongle operations. Not sure how much other state hogp actually needs.)
@benedekkupper can you elaborate on its feasibility and difficulty?