1
mirror of https://github.com/mpv-player/mpv synced 2024-11-03 03:19:24 +01:00
mpv/DOCS
Uoti Urpala 5c4b059f16 input: rewrite -key-fifo-size limiting logic
Instead of strictly limiting the number of total entries in the
internal fifo, make the overall buffer bigger and try to limit entries
based on how many bound commands they're expected to generate. Now
doubleclick and button down events aren't counted for that limit.
Normally the sequence down-doubleclick-up generates at most one
command, so this better matches the quantity we actually want to
limit. Also add a mechanism to clear the button combination state kept
by input.c when the fifo is full; this avoids "stuck button" problems
due to button release events being dropped.

The key combination state clearing is partially based on MPlayer 1
changes by Reimar Döffinger (though overall the effects of this commit
are quite different). It still doesn't make "stuck button" problems
completely impossible; at least if the VO gets closed while a button
was down then nothing will send a button up event or reset state.
2011-05-02 00:44:21 +03:00
..
man input: rewrite -key-fifo-size limiting logic 2011-05-02 00:44:21 +03:00
tech vidix: drop VIDIX support 2011-01-31 16:03:10 +02:00
xml DOCS/xml/en: remove various outdated documentation 2011-02-15 12:08:16 +02:00
default.css the great MPlayer tab removal: part I 2010-04-12 10:56:17 +00:00
README Do not build monolithic documentation in a separate directory. 2009-12-13 22:51:55 +00:00

#######################################
## Reading the MPlayer Documentation ##
#######################################

Thanks for reading MPlayer documentation !!!


1. For "release" version users (i.e. non-Subversion):

   a, Enter the HTML/ directory, and there you'll find the documentation,
      each language in its own subdirectory.

   b, If you prefer reading the documentation as a single big file it
      can be found in the file MPlayer.html, each language in its
      own subdirectory.

   c, If the HTML/ directory does not contain your language,
      try the subdirectories in this very same folder.


2. For "development" version users (i.e. Subversion or Subversion snapshots):

   a, Enter the xml/ directory, and read the README file there to find
      out how to build a HTML version of the XML documentation. It will
      be created in the HTML/ directory.

   b, If the xml/ directory doesn't contain your language, try the
      subdirectories in this very same folder.