- 17 Jan, 2008 14 commits
-
-
Antoine Cellerier authored
-
Pierre d'Herbemont authored
-
Ilkka Ollakka authored
maininputmanager which listens p_intf->p_libvlc "volume-change" variable for volumechange. ref #1365
-
Pierre d'Herbemont authored
-
Ilkka Ollakka authored
biggest polls in qt4-interface, still maybe few to go. ref 1365
-
Pierre d'Herbemont authored
-
Rafaël Carré authored
-
Rafaël Carré authored
-
Ilkka Ollakka authored
vlc:nop->vlc:skip revert was unintented.
-
Rafaël Carré authored
-
Rafaël Carré authored
"state" is an integer, not a boolean (since vlc_bool_t is an int, that only makes the code clearer to read)
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
Qt4 - Preferences: avoid a few segfaults in the hotkeys selector. Avoid using QList of module_config_t and attack it from different classes. Avoid using some useless casts...
-
- 16 Jan, 2008 26 commits
-
-
Christophe Mutricy authored
-
Christophe Mutricy authored
-
Christophe Mutricy authored
-
Christophe Mutricy authored
-
Rémi Denis-Courmont authored
-
Damien Fouilleul authored
vlc security: As i've seen very little improvement on that front, i've decided to check in my take on handling the problem of managing harmful options. I'm pretty sure this is going to be very controversial, but I think my approach is quite simple and yet very effective Anyway, my approach makes the following assumptions: - most vlc options are considered safe, only a handful are particularily unsafe and need be declared as such in their definition (they mostly deal with writing to an output file or URL) - unsafe options are only considered potentially harmful when used as an input option, ie. the ':option' format. Configuration options are always considered safe 'i.e --option' - unsafe options are associated with a global security policy, which dictates how these are handled. At the moment, The policy can be either block, allow or prompt, and is set using the '--security-policy' option (which itself is considered unsafe ;) the policy can be set by the user at the command line or in the preferences, it curently defaults to prompt, which is the desirable state for deskop use. However, it can be overriden depending on context, for example, the activex and mozilla will force the security-policy to block regardless of preference settins. the code is a bit rough at the moment, but i will optimize/clean it up if the dev community this approach is worth keeping. try the following example, and you'll see quickly what i mean: ./vlc -vvv <a mrl> :sout=#transcode{vcodec=mp1v,vb=1024,acodec=mpga,ab=192}:standard{mux=ts,dst=vlc-output.ts,access=file}" Enjoy, Damien
-
Rémi Denis-Courmont authored
-
Christophe Massiot authored
-
Rafaël Carré authored
-
Rémi Duraffort authored
-
Rémi Duraffort authored
-
Rémi Duraffort authored
-
Rafaël Carré authored
-
Rafaël Carré authored
-
Pierre d'Herbemont authored
-
Rafaël Carré authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
-
Jean-Baptiste Kempf authored
Ouf!
-
Pierre d'Herbemont authored
MacOSX/Framework/VLCMedia.m: Make sure we compare the media_descriptor and not the url, as we can have two perfect different media (different meta, different option), but with the same url.
-
Pierre d'Herbemont authored
-