- Mar 14, 2025
-
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
-
- Mar 13, 2025
-
-
Wrong alignment: GEN util/qmldir GEN widgets/qmldir MOC dialogs/bookmarks/bookmarks.moc.cpp MOC dialogs/dialogs/dialogmodel.moc.cpp UIC dialogs/extended/ui_video_effects.h UIC dialogs/firstrun/ui_firstrunwizard.h
-
-
The output value is bounded by the size parameter, and is used for indexing elements in arrays.
-
Regression from fe26ba9b.
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
We do not need/do not access the library window at all here Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
As we re-navigate through these nodes we will re-generate their parents and get a correctly re-linked tree with new versions of these same orphan nodes, so this is fine Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
generateChildNodesForDirectoryNode already does this Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Fixes EINVAL returned by vlc_gl_sub_renderer_Prepare() Fixes regression from 2b6405c7
-
This reverts commit 37f01a65.
-
This reverts commit 185d3fba.
-
-
- Mar 12, 2025
-
-
-
That should allow using ninja to build libvlc.so on Android (it uses 300+ .a files). This is part of ninja 1.12 which doesn't have proper jobserver support.
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
- Mar 11, 2025
-
-
- Mar 10, 2025
-
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com> fv Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
In b1e11641, we started to delay requesting the blur effect for the interface window. This was only because of Wayland, as without delaying the blur effect could not be activated. Even though this problem only occurred with Wayland (I'm not sure if it is a KWin Wayland thing, or a KWindowSystem Wayland thing), the code for delaying requesting the blur effect was not made conditional to simplify things as it is generally fine to have the effect as soon as the window gets activated. With 874925c0, we disabled using redirection surface on Windows when Direct Composition is used. This makes the window completely transparent. In early 2025, Chromium started doing the same [1]. However, they mention that it is better to have the blur effect before the window is ready: > Since the browser window appears before the GPU > process is able to draw content into it, the > acrylic effect gives the user feedback that a > window is present and content is coming. Without > the acrylic effect a transparent window will > appear with a 1 pixel border that eats all mouse > clicks; not a good user experience. Further, > the acylic effect will appear in uncovered regions > of the window when the user resizes the window. Since we have the same "problem", I propose delaying requesting the blur effect only when necessary, i.e. on Wayland. I have previously checked that on X11 and Windows this was working fine. This also makes us aligned with the behavior of Chrome browser, along with other applications that are going to follow it. [1] https://chromium-review.googlesource.com/c/chromium/src/+/6143173
-
- Mar 09, 2025
-
-
It seems that `TableViewDelegate` was forgotten to be added here.
-
Qt 6.9 introduces `TableViewDelegate` in Qt Quick Controls, this causes name conflict here as the import is not explicitly stated when resolving `TableViewDelegate` in `TableViewExt.qml` currently. Alternatively the name can be kept, and `Widgets.TableViewDelegate` can be used to specify which `TableViewDelegate` to use, but this is probably safer than that approach.
-
Steve Lhomme authored
-