The framerate as specified by the user or detected by the v4l2 access input was
overwritten by the rawvideo decoder. The module did not specify:

	es_fmt.video.i_frame_rate
	es_fmt.video.i_frame_rate_base

Their default values are 0. The rawvideo decoder detects that there is no framerate
specified and resorts to its own default (fps 25.0). Through setting framerate and
framerate_base in the v4l2 es format the correct fps is communicated to vlc core.

The framerate reduction code is not needed. If the user did not set
the requested framerate, then the v4l2 module asks the driver for its
default value. When fps is specified by the user then that one is used.

This reverts commit e1d4b62a.

Signed-off-by: Felix Paul Kühne <fkuehne@videolan.org>

Sure, naming a static library *_static.a is _VERY_ useful
(and helps the linker find it... not)
And of course, installing .svn on make install is clever

Do not ask me why noone uses MPC these days...

Some people want to seek backward, resume and pause again at end-of-stream.

Signed-off-by: Pierre d'Herbemont <pdherbemont@free.fr>

Up to now, text control could but be focusable, and this focus was used
to scroll text, should it be too long for full display.

From a user viewpoint, this behavior is often counterintuitive :
 - Most of the time, the control is designed to fit the text anyway, and
   scrolling is not expected.
 - On the other hand, an underlying control may be used to move the window
   (for instance, the title bar), and a text control is expected not to
   interact in this endeavor. Same goes for popupmenu, that is expected
   to work if one happens to right-click on a text control.

This patch adds a 'focus' attribute to the text control, and leave it to the
skins developper to decide which behavior is most desirable on a per-control
basis. focus still defaults to true to maintain skins current behavior.

Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

Signed-off-by: Rémi Denis-Courmont <remi@remlab.net>

Return a 413 error instead of crashing

This caused genuine bugs like mangled bodies and corrupted requests
(usually leading to 501 errors), and possibly leaks of memory buffer
of the size of the Content-Length parameter. This is pretty bad since
crafted requests could easily exhaust the memory and/or trigger a crash.
Apart from the contents of the buffer of the involved request, there
doesn't seem to be any possible memory corruption.

This fixes a regression brought by 7f485998

On skins2(tested on Linux), open and close the preferences dialog leads to a
crash, because the whole qt4 thread terminates unexpectedly.

This is due to setQuitOnLastWindowClosed set to true. As a dialog provider,
qt4 doesn't run any windows, and therefore just closing the preferences
 dialog box (via accept() or reject()) signals the qt4 thread to quit.

8554 is the IANA-registered RTSP alternative port

- setContentMargin is the same on all platforms
- color fixes on Linux