- Jul 24, 2022
-
-
the alias matches the filename
-
- Jul 14, 2022
-
-
- Jul 12, 2022
-
-
This reduce the number of intermediary FBO and shader passes
-
- Jul 02, 2022
-
-
Co-authored-by:
Pierre Lamot <pierre@videolabs.io>
-
- Jul 01, 2022
-
-
- Jun 26, 2022
-
-
-
We also update the EmptyLabel implementation to make it generic.
-
- Jun 11, 2022
-
-
- May 31, 2022
-
-
- May 17, 2022
-
-
-
a generic ML context model
-
can be used to create native menus with support asyncronously retreive data from MLBaseModel like model
-
QtObject which supports direct children
-
- May 14, 2022
-
-
- Apr 29, 2022
-
-
Visiblity -> Visibility.
-
- Apr 28, 2022
-
-
this allow to keep the playlist visible when switching between the player and the medialibrary views, regarding the different parameters (playlist docked, playlist visible, video embed) this uses a hierarchical state machine to track the different states and transitions.
-
- Apr 22, 2022
-
-
- Apr 15, 2022
-
-
- Apr 07, 2022
-
-
- Apr 01, 2022
-
-
- Mar 17, 2022
-
-
It's using IID_PPV_ARGS and WRL.
-
- Mar 14, 2022
-
-
- Mar 13, 2022
-
-
- Mar 11, 2022
-
-
- Mar 05, 2022
-
-
This gives a table listing all options, similar to and inspired by the `about:config` interface in Firefox. Unique benefits: - It highlights which options have been modified from default state. - It allows selective resetting of individual options to default values. Support is included to toggle booleans with a simple double-click. Double-clicking on other types opens the edit dialog. For colour selection items, the modify action directly opens the Qt colour selection dialog rather than present the colour control used in the advanced preferences view, since this is much cleaner. Note that the existing simple and advanced views are not linked; if you change an option in one view, that change is not reflected in the other, and saving changes only uses the state from the selected view. The same is currently true of the new expert mode, though I plan to later change this behaviour (for all three). Note also that hotkey items are deliberately excluded from this view. The dedicated hotkey editor is best suited to managing hotkeys. It does not work well to include the set of 224 unique hotkey options within this table, especially since we'd have to duplicate the code checking for duplicate assignments if we allow editing of them as with all other option types within this interface. It may seem odd for the 'expert' mode to be the only one without hotkey editing, however the hotkey editor does not really fit well into 'advanced' mode either, and I have plans to propose separating the hotkey editor entirely from within the set of three views in a small redesign. Fixes #18607.
-
- Feb 20, 2022
-
-
- Feb 13, 2022
-
-