Concurrent device access causes interference between programs about solaar

[pwr]

The device index/type/register have to be matched anyway to recognize the reply (see lib/logitech/unifying_receiver/base.py:request()). Same goes when receiving an 0x8F reply. The initial request messages are also randomized whenever possible (usually HID++ 2.0 requests).

As for making the messages asynchronous, it would complicate the way the app works way too much. Usually when making a request, from whatever thread (and the Gtk GUI thread is the most sensitive to this), you need the reply right away to work with it.

Also, threading in python is... not great. Right now there's a separate thread just listening for events from the receiver/devices, the other requests are made in whatever thread needs the reply. In previous versions I've tried different solutions, and this one appears to work best so far, at least within the application.

[pwr]

Now that the 0.9 release is coming up, I've done a review of the behaviour of Solaar when solaar-cli is run in parallel. Tried listings, pairing and unpairing, and in all cases the state was correctly updated in the running Solaar.

If no more errors are reported by next week, will close this bug.

[jrbenito]

If no more errors are reported by next week, will close this bug.

Long time has passed. @Lekensteyn , is this still valid?

[Lekensteyn]

I guess that the matching of responses againsts requests should be sufficient.