area->vdcfg is always set to the display size received from the core.

When rendering to NV12/P010 otherwise we only need one.

We don't need to know anything about the display module in Common code. Only
the Init needs to keep track of the source video format.

So we don't have to pass the display module at each UpdateRects nor the source
video_format_t. It may also change if the texture is bigger than the decoded
size (D3D11 extra padding).

They always cover the same (window) area so there's no reason to use two.

We do not need to know the first placement of the video window. It's always
shown (black) from the start now.

It is always true now that all modules have been fixed to properly place the
textures.

We will never copy more than the visible area (plus one if the source is an
odd dimension).

We cannot rely on the output always having the exact aspect ratio of the video.
So we draw on the whole window area and place the video accordingly.

Right now all Windows display module render on the hvideownd which is already
cropped and positioned according to the PlacePicture results.
In external rendering we do not have this mechanism and so we need to be able
to render on the full display but cropping according to the PlacePicture result.

Ultimately that should be the only mode. D3D and OpenGL should have no problem
cropping and stretching in the proper area. WinGDI should also be able to only
draw on a portion of a HWND. It can already stretch.

This is handled in the vout window modules, not in the display modules anymore.

Sergey Radionov authored 5 years ago and Steve Lhomme committed 5 years ago

to be able display frames correctly

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

Rémi Denis-Courmont authored 5 years ago and Steve Lhomme committed 5 years ago

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

Abel Tesfaye authored 5 years ago and Steve Lhomme committed 5 years ago

The sub menu located at media -> open recent media used to be empty. This commit fixed that.

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

FeRD (Frank Dana) authored 5 years ago and Steve Lhomme committed 5 years ago

The MPRIS2 introspection metadata contained several errors and
omissions inconsistent with the official MPRIS2.2 spec:
- The Player.Position property should be type 'x', not 'i'
- The Player.Shuffle property should be type 'b', not 'd'
- The Player.{Minimum,Maximum}Rate properties should be read-only,
  not read-write
- The Player.CanGo{Next,Previous} properties were not declared,
  despite being implemented
- The Player.Seeked signal was not declared, despite being emitted

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

FeRD (Frank Dana) authored 5 years ago and Steve Lhomme committed 5 years ago

The metadata in dbus_introspection.h was listed neither in
alphabetical order, nor in the same order used in the MPRIS2
specification. This commit reorders elements to match the spec,
making reconciliation easier. No changes made to any element.

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

+ cleaning

Fixes the QtANGLE not included properly in the original .pc file.

Fixes QTBUG-75495

Fixes QTBUG-75468

Not just for cross compilation.

Only the wine call differs from 0003-allow-cross-compilation-of-angle-with-wine.patch

Not just for cross-compilation.

The extraction path has changed in 004e367b