Benjamin Arnaud authored 2 years ago and Felix Paul Kühne committed 2 years ago

We also update the EmptyLabel implementation to make it generic.

Prince Gupta authored 2 years ago and Hugo Beauzée-Luyssen committed 2 years ago

a generic ML context model

Prince Gupta authored 2 years ago and Hugo Beauzée-Luyssen committed 2 years ago

can be used to create native menus with support asyncronously retreive data from MLBaseModel like model

Prince Gupta authored 2 years ago and Hugo Beauzée-Luyssen committed 2 years ago

QtObject which supports direct children

Romain Vimont authored 2 years ago and Rémi Denis-Courmont committed 2 years ago

Visiblity -> Visibility.

Pierre Lamot authored 2 years ago and Jean-Baptiste Kempf committed 2 years ago

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.

Steve Lhomme authored 3 years ago and Hugo Beauzée-Luyssen committed 2 years ago

It's using IID_PPV_ARGS and WRL.

Lyndon Brown authored 5 years ago and Jean-Baptiste Kempf committed 3 years ago

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.

Benjamin Arnaud authored 3 years ago and Hugo Beauzée-Luyssen committed 3 years ago

After this, groups will be hidden until we bring them back in VideoAllDisplay.