- Mar 07, 2025
-
-
Enrico Weigelt, metux IT consult . authored
-
Enrico Weigelt, metux IT consult . authored
-
Enrico Weigelt, metux IT consult . authored
Not used by any drivers (just the xcmisc extension), so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any drivers (just the xcmisc extension), so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any drivers/modules, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any external drivers, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any external drivers, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used in any external modules, so no need to keep it public. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any external drivers, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any external drivers, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used in any external modules, so need to keep it public. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Little helper function for checking whether a resource XID belongs to the server itself. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Almost all callers have ClientPtr anyways, so we're just doing duplicate array lookups. Just using ClientPtr directly is easier anyways. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
The function actually operates on ClientRec, so we can pass it in directly, so it doesn't need to fetch it from clients[] array itself. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Retrieves the ClientPtr for the owner of given resource. This way reducing the sites directly accessing clients[] array. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
We can write down the function name directly. Nobody else than a few define's in here using that macro. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Make it type-safe and a bit more obvious what it really does, also adding some inline documentation. Since it's just some bit shifting magic, it's qualified for inlining. The CLIENT_ID() macro isn't used by any external modules, so the new function doesn't need to be in a public header. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Helper function for retrieving the owning client of an OtherClients. It's an actual function, so callers don't need access to internal knowledge (definition of struct _OtherClients, clients[] array, ...) Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Helper function for retrieving the owning client of an InputClients. It's an actual function, so callers don't need access to internal knowledge (definition of struct _InputClients, clients[] array, ...) Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Helper function for retrieving the owning client of a grab. It's an actual function, so callers don't need access to internal knowledge (definition of GrabRec, clients[] array, ...) Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Hide internals (drop the need to include windowstr.h), make it typesafe as well as the naming easier to understand. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Nobody using it anymore. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Nobody using it anymore. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Nobody using it anymore, so no need for keeping it around. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
The supported platforms already have asprintf() and vasprintf(), so there's no need for having our own implementation anymore. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
No need to directly hard-crash the Xserver when strdup() fails, instead try to handle the situation gracefully. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
No need to hard-crash the whole server if some strdup() calls failing, those fields already may be NULL, so consumers can handle that situation. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
No need for RunXkbComp() to hard-crash (by calling XNFstrdup()) the server if strdup() fails to allocate more memory - it's callers already handling the situation gracefully. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
-
Enrico Weigelt, metux IT consult . authored
-
Enrico Weigelt, metux IT consult . authored
No used outside of xkb, so no need to keep it in public API header. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Not used by any drivers/modules, so no need to keep it exported. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
Last commit from 2016, almost a decade ago, seems dead. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
FIXME: the type LOCO is still used by certain drivers - but only a pointer to it. We'll first have to introduce an opaque pointer type and convert those drivers, before we can drop LOCO from public interface. This reverts commit 658e83f8.
-
Enrico Weigelt, metux IT consult . authored
Not used by any external module/driver, so no need to keep it in public header. Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
-
Enrico Weigelt, metux IT consult . authored
Within the Xserver build, there's always dix-config.h Signed-off-by:
Enrico Weigelt, metux IT consult <info@metux.net>
-
Enrico Weigelt, metux IT consult . authored
-