lavc's is marked as experimental

It seems that some avcodec decoders release frames even after being flushed.

It (probably) happens only when the video is non mod 16, or non mod 32
with YV12 hardware surface.

Signed-off-by: Laurent Aimar <fenrir@videolan.org>

Used SetCapture/ReleaseCapture to emulate what x11 seems to do by default.

It is not limited to win32.

Add a channel list widget at the left of the EPGView widget.
Remove the splitter on the EPG window.

This reverts commit eca93931.
and fixes taglib compile

This reverts commit 61db9aad.

untested

untested

untested

untested

Matroska : Set default compression type for the ContentCompAlgo element to 0 (indicating zlib). Some muxers (for example mkvmerge v4.0.0) do not write ebml elements which correspond to the default values (as defined in the spec).
Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Use currently unused code to sort subtitle lines after they have been loaded.
Closes #3734.

It should improve the transition.

As a side effect, window class names are now uniques (process wide)
allowing to unregister them and so to unload properly the msw vouts.

Unlike _endthread and ExitThread, _endthreadex doesn't close the handle.
It is therefore up to the caller to close it. Hence no need for an extra
handle duplication (that mostly amounted to a memory leak when the normal
 path was used, i.e normal return from thread with implicit _endthreadex)

According to msdn doc, _endthreadex(0) is to be used when thread is
 launched with _beginthreadex().

Note that when returning from the normal path, an implicit _endthreadex is
issued anyway.  It is important to be consistent whatever the path, since
those final functions (_endthread, ExitThread, _endthreadex) don't have
the same deallocation policy.

As we use AC_PATH_PROG, if you want to force LUAC by specifying it on your command line you need to give a full path+exec_name. Which is a bit un friendly. So work-around this behaviour.

For lack of a faster detection (based on win32 api messages),
resize/move of the parent window are detected in the Manage function
on a regular basis and acted upon if need be.

Move is an issue only for directx (surface doesn't automatically follow
the associated window). Though coordinates doesn't change, an UpdateRects
is still required to update the various rectangles used by directx.

As it was coded, everything was already taken care of.
The artificial "shaking" of the window was quite useless.