- Apr 30, 2019
-
-
François Cartegnie authored
refs broken #22228
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
-
François Cartegnie authored
that really can't work due to empty segments and be fixed without big changes
-
François Cartegnie authored
pretty useless since we can no longer change it...
-
François Cartegnie authored
-
François Cartegnie authored
-
Steve Lhomme authored
In that case we don't call CommonInit. We also check that on Winstore the legacy "winrt-d3dcontext" variable is set if an external callback is not used.
-
Steve Lhomme authored
During fast resizing we might get a lot of WM_SIZE messages which are each sending a CHANGE_DISPLAY_SIZE which may take time to get to the display thread. We bypass a part of this lag by reading directly the current size of our parent HWND (since we always place our HWND at 0,0 with the full size). This is similar to what we have before when we handled all the HWND in this part of the code. We read the window size directly on each size change.
-
Steve Lhomme authored
The dimension to use is always set in area->vdcfg.display. The hwnd size always matches this size since we resize it accordingly for each DISPLAY_CHANGE_DISPLAY_SIZE call. There is a slight delay between the moment the window tells the core of the size change and the moment it's effective in the display. So resizing quickly is not as smooth as when reading the HWND size directly.
-
Steve Lhomme authored
Implement the TODO: call a DISPLAY_CHANGE_DISPLAY_SIZE when we detect the external swapchain dimensions have changed. We don't need a special callback to read the "display" dimensions.
-
Steve Lhomme authored
At some point this code should go away.
-
Steve Lhomme authored
area->vdcfg is always set to the display size received from the core.
-
Steve Lhomme authored
When rendering to NV12/P010 otherwise we only need one.
-
Steve Lhomme authored
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.
-
Steve Lhomme authored
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).
-
Steve Lhomme authored
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.
-
Steve Lhomme authored
It is always true now that all modules have been fixed to properly place the textures.
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
We will never copy more than the visible area (plus one if the source is an odd dimension).
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
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.
-
Steve Lhomme authored
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.
-
Steve Lhomme authored
-
Steve Lhomme authored
This is handled in the vout window modules, not in the display modules anymore.
-
to be able display frames correctly Signed-off-by:
Thomas Guillem <thomas@gllm.fr>
-
Signed-off-by:
Thomas Guillem <thomas@gllm.fr>
-
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>
-
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>
-
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>
-
Steve Lhomme authored
+ cleaning
-
Steve Lhomme authored
Fixes the QtANGLE not included properly in the original .pc file. Fixes QTBUG-75495
-
Steve Lhomme authored
Fixes QTBUG-75468
-
-
Steve Lhomme authored
Not just for cross compilation. Only the wine call differs from 0003-allow-cross-compilation-of-angle-with-wine.patch
-