12 Commits (9e22f3bf1cca9a957173193250eaeb084ab0c245)

Author	SHA1	Message	Date
Romain Vimont	9e22f3bf1c	Replace unsigned char by uint8_t for buffers ... For consistency.	3 months ago
Romain Vimont	fa5b2a29e9	Add missing SC_ prefix to header guards	2 years ago
Romain Vimont	2a0730ee9b	Add device clipboard set acknowledgement ... Add a device message type so that the device could send acknowledgements for SET_CLIPBOARD requests. PR #2814 <https://github.com/Genymobile/scrcpy/pull/2814>	3 years ago
Romain Vimont	30e619d37f	Replace SDL_strdup() by strdup() ... The functions SDL_malloc(), SDL_free() and SDL_strdup() were used only because strdup() was not available everywhere. Now that it is available, use the native version of these functions.	3 years ago
Romain Vimont	ab912c23e7	Define feature test macros in common.h ... This enables necessary functions once for all. As a consequence, define common.h before any other header.	3 years ago
Romain Vimont	59feb2a15c	Group common includes into common.h ... Include config.h and compat.h in common.h, and include common.h from all source files.	3 years ago
Romain Vimont	488d22d4e2	Increase clipboard size from 4k to 256k ... Beyond 256k, SDL_GetClipboardText() returns an empty string on my computer. Fixes #1117 <https://github.com/Genymobile/scrcpy/issues/1117>	4 years ago
Romain Vimont	245999aec4	Serialize text size on 4 bytes ... This will allow to send text having a size greater than 65535 bytes.	4 years ago
Romain Vimont	d91c5dcfd5	Rename MSG_SERIALIZED_MAX_SIZE to MSG_MAX_SIZE ... For simplicity and consistency with the server part.	4 years ago
Romain Vimont	8f314c74b0	Reorganize message size constants ... Make the max clipboard text length depend on the max message size.	4 years ago
Romain Vimont	1f8ba1ca79	Include config.h everywhere ... Ref: <https://github.com/Genymobile/scrcpy/issues/829> Suggested-by: Louis Kruger <louisk@gmail.com>	5 years ago
Romain Vimont	28980bbc90	Rename "event" to "message" ... After the recent refactorings, a "control event" is not necessarily an "event" (it may be a "command"). Similarly, the unique "device event" used to send the device clipboard content is more a "reponse" to the request from the client than an "event". Rename both to "message", and rename the message types to better describe their intent.	5 years ago