- Jul 07, 2017
-
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
seems there since sout = object_find() was removed
-
François Cartegnie authored
osdmenu module was removed a long time ago
-
Signed-off-by:
Victorien Le Couviour--Tuffet <victorien.lecouviour.tuffet@gmail.com> Signed-off-by:
Thomas Guillem <thomas@gllm.fr>
-
- Jul 06, 2017
-
-
Signed-off-by:
Thomas Guillem <thomas@gllm.fr>
-
Signed-off-by:
Jean-Baptiste Kempf <jb@videolan.org>
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
refs #18495
-
François Cartegnie authored
-
François Cartegnie authored
workarounds invisible overlay menus/highlight refs #5055
-
François Cartegnie authored
-
Thomas Guillem authored
-
- Jul 05, 2017
-
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
Thomas Guillem authored
-
Thomas Guillem authored
-
François Cartegnie authored
now goes through pf_ 8728715d
-
Signed-off-by:
Francois Cartegnie <fcvlcdev@free.fr>
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
Thomas Guillem authored
Use the VADisplay from the src pic and not upload one (that is NULL in case of download).
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
Apply the filter setting *after* initializing the context. Signed-off-by:
Jean-Baptiste Kempf <jb@videolan.org>
-
Thomas Guillem authored
Favor DRM and use X11/WAYLAND if it's not available. Fixes #18445
-
Thomas Guillem authored
This fixes undefined behaviors when the native display is destroyed before the VADisplay is terminated. This caused a crash or invalid surfaces with the DRM native display when changing between 2 vouts. For X11, no crashes were observed, probably because the native display was already hold by the window.
-
Thomas Guillem authored
These values are always positive.
-
According to the spec, calloc can return a NULL or a unique pointer value if either of the arguments are 0 depending on the implementation. Add a guard to prevent allocation by returning an error in the above case. Signed-off-by:
Thomas Guillem <thomas@gllm.fr>
-