- 25 Aug, 2009 10 commits
-
-
Rémi Duraffort authored
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Ilkka Ollakka authored
should fix that returning from fullscreen going wrongsize, also set fullscreen flags after reparent and before parenting back from fullscreen.
-
Ilkka Ollakka authored
screennumbers starts from 1 onward, this allows user again to define if he wants fullscreen window on particular screen instead of the one where interface is.
-
Pierre d'Herbemont authored
configure: Add implicit sequence-point return-type strict-aliasing array-bounds missing-parameter-type overflow int-to-pointer-cast pointer-to-int-cast div-by-zero overflow to the list of Werror warnings.
-
Pierre d'Herbemont authored
-
Pierre d'Herbemont authored
-
Sébastien Escudier authored
Signed-off-by: Pierre d'Herbemont <pdherbemont@free.fr>
-
- 24 Aug, 2009 30 commits
-
-
Pierre d'Herbemont authored
-
Niles Bindel authored
Added some additional locking to the media list player playitem functions to prevent threading instability. Signed-off-by: Pierre d'Herbemont <pdherbemont@free.fr>
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Laurent Aimar authored
-
Laurent Aimar authored
-
Laurent Aimar authored
Revert "nuv: Fix some warnings and fix an issue where some unitialized pointer access could lead to a crash." This reverts commit 3bbe374b. This commit is wrong. There was no risk of crash. I will add assert instead when not obvious.
-
Laurent Aimar authored
-
Laurent Aimar authored
This reverts commit 13268071. It is wrong as -1 and 0 does not have the same meaning for picture_Export. (I will document it).
-
Laurent Aimar authored
-
Laurent Aimar authored
-
Laurent Aimar authored
This reverts commit 260dd07f. It is useless, the variable cannot be uninitialized, and does not generate a warning for me. The patch could prevent finding real bug if the code is modified.
-
Laurent Aimar authored
-
Sébastien Escudier authored
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>
-
Rémi Denis-Courmont authored
-
Sébastien Escudier authored
VLM : move input event callback deletion. In order to receive all inputs events it's better to delete callbacks just before releasing the object. Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>
-
Rémi Denis-Courmont authored
-
Rémi Denis-Courmont authored
...and fix a memory leak in LUA
-
Rémi Denis-Courmont authored
-
Rémi Denis-Courmont authored
-
Rémi Denis-Courmont authored
This will avoid adding plenty of config_GetFoobarDir exports later. Also make config_GetHomeDir return a heap-allocated string.
-
Hugo Beauzee-Luyssen authored
Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>
-
Erwan Tulou authored
-
Erwan Tulou authored
-
Erwan Tulou authored
This patch does the following : - as a vout window provider, make sure skins functions run by vout thread(s) don't issue any calls to the GUI. (skins on Linux runs fine at last !) - prepare support for SET_VOUT_SET_FULLSCREEN new control - implement hotkeys (no longer available at the vout level) - modify a show() method not consistent across platform - cleanup (dead code)
-
Erwan Tulou authored
-
Erwan Tulou authored
skins2: avoid deadlock when audio-visual is used (accounts for vlc often but not always hanging in this case) Audio-visual holds the audio_mixer lock during its initialization phase which includes initialization of the vout. On the other hand, skins polls every 10ms to check change in the audio volume (this also requires holding the audio_mixer lock) This leads to a frequent deadlock at the skins level. The patch stops polling w.r.t volume and rather reacts on change signalled by the core via a callback. This makes deadlock occurence almost nil. A long term solution could be that 1/ audio_visual doesn't keep on holding the lock during vout initialisation and 2/ skins stops polling every 10ms for a whole bunch of things (rather use callbacks as qt4 does)
-
Erwan Tulou authored
This problem appeared in vlc1.1. setting volume from core or from the user slider must be differentiated, as sending back a zero value (mute) tells the core to really set value to zero (thus erasing the saved volume) this patch reuses what is already done for position slider (similar issue)
-