- Jun 01, 2024
-
-
-
-
-
Under some circumstances, the application won't close after a quit event. Using an `exit` in `triggerQuit` callback ensure that the application won't prevent the mainloop to quit. At this point, both the gui and vout are stopped
-
-
-
The expose event is emitted after a resize, thus this not necessary to monitor width/height events on the main window
-
-
-
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
macosx: Remove handling for VLCLibraryCollectionViewAudioGroupSupplementaryDetailView in VLCLibraryCollectionViewFlowLayout Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
NSNotificationCenter was used repeatedly with repeated allocation to the autorelease pool in order to setup the suffix addition for the notification name. This commit uses a for-loop releasing the local autorelease allocations and create the notification names on-the-fly to avoid repetition.
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Windows 11 identifies as Windows 10 (NT 10), so this comparison always yields false. As a side note, native acrylic background for Win32 windows only gained support with the Windows 11 22H2 update, that's why there is the check here. Note that according to the general conventions a transparent window must be frameless on Windows. This is currently not the case, because "frameless window don't support areo snapping". So, it can be considered as a known bug if native acrylic does not work as intended. This grants a requirement of change to use frameless window, and get rid of the current workaround that simulates frameless window in mainctx_win32.cpp. If aero snapping does not work, it is Windows's problem since we are using frameless windows in every other platform.
-
- May 30, 2024
-
-
-
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
- May 29, 2024
-
-
- May 28, 2024
-
-
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>
-
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>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
-
- May 27, 2024
-
-
-
Steve Lhomme authored
They can be added back later if needed.
-
macosx: Use accessibility description for input node path control items as path control item identifiers The input node path control items are readable strings but can be used as identifiers thanks to the fact the contain the path for the given input node. This is a big ugly hack but we have no other option to make input node path control items identifiable, as we receive different instances from the nspathcontrol that are not our subclass Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-
Signed-off-by:
Claudio Cambra <developer@claudiocambra.com>
-