mirror of https://github.com/tuhiproject/tuhi.git
caa52e0c51
This is what the dbusserver module does as well, so we end up with a weird mismatch: to the base module the device is still known and unregistered on the next search start. So when we see the bluez properties float past, we don't add a new devices. To the dbusserver the device is gone though and since we don't add it again in the base module, we never send a signal for it. Since there's a reasonable assumption that if we don't register the device, we don't want it anyway, let's delete it from the base device list too. This doesn't fix the issue of a device timing out while waiting for a button press. That device will count as known until the next search stop. But at least now we don't have to restart tuhi. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| base.py | ||
| ble.py | ||
| config.py | ||
| dbusserver.py | ||
| drawing.py | ||
| uhid.py | ||
| wacom.py | ||