Romain Vimont 4963b468cb Introduce non-droppable control messages
Control messages are queued from the main thread and sent to the device
from a separate thread.

When the queue is full, messages are just dropped. This avoids to
accumulate too much delay between the client and the device in case of
network issue.

However, some messages should not be dropped: for example, dropping a
UHID_CREATE message would make all further UHID_INPUT messages invalid.
Therefore, mark these messages as non-droppable.

A non-droppable event is queued anyway (resizing the queue if
necessary, unless the allocation fails).

PR #5270 <https://github.com/Genymobile/scrcpy/pull/5270>
2024-09-13 22:03:02 +02:00
..
2024-07-19 17:48:39 +02:00
2024-08-01 18:15:37 +02:00
2024-06-23 19:15:45 +02:00
2024-09-13 22:03:01 +02:00
2024-08-02 22:32:04 +02:00