To start interfaces with the `interface server" capability.
This command is separated fromt `intf" to make a clearer distinction
with server interfaces.

This menu's purpose is to start server interfaces on the fly.
View is not really the right place to put this but at the moment we'll
keep that way to stay consistent with the already existing
`View/Interfaces" menu.

To make a very distinct difference between usual interfaces and
interfaces that might expose content or main player controls to the
network.
Making this distinction make sure no potentially harmful interface is
accidentally launched with `--extraintf` or even `-I` (the previously
introduced `--server` should be used instead). It will also help the GUI
modules to introduce proper measures to inform the users that the
interface they'll launch might expose private data on the network.

To make the difference with normal interfaces and interfaces that might
expose control to the network.
Note that as opposed to `--extraintf` and `--control`, the `--server`
module list option is volatile, meaning that it can't be saved as a
default in the configuration files.
A new `server interface" capability is also to be introduced.

In the near future some other capabilities might appear for different
interfaces behaviors.

The previous calculation was wrong and could lead to two potential
issues:
 - Too much wake/sleep because the block remaining data is very small
 - Too long sleep, if the block is longer than the buffer size, that
   could lead to underrun

To fix this issue, use the same sleep calculation than wasapi.

Niklas Haas authored May 02, 2021 and Hugo Beauzée-Luyssen committed May 06, 2021

This WAYLAND_CFLAGS was probably meant to be WAYLAND_CLIENT_CFLAGS. The
former doesn't exist on my system, the latter is required for
compilation to succeed.

Lyndon Brown authored Apr 18, 2019 and Pierre Lamot committed May 05, 2021

as per comment, these have no relevance to GUI prefs

Lyndon Brown authored Apr 08, 2019 and Pierre Lamot committed May 05, 2021

this includes a fix for the following flaw: if for any reason a
set_subcategory() call followed by no options was ever placed at the end
of the core option set, then this would have dereferenced memory beyond
the end of the set. (Note that such empty entries currently genuinely
exist in order to ensure that respective tree nodes are created for
modules to attach to, which will be fixed later).

Lyndon Brown authored Apr 09, 2019 and Pierre Lamot committed May 05, 2021

saves wasting effort

Lyndon Brown authored Mar 23, 2019 and Pierre Lamot committed May 05, 2021

(add common defines for specifying hidden category/subcategory)

Fix a regression introduced in
adfe2249
Fix #25605

Increase to 300M to allow to build universal releases.
This is the maximum size of the release image, the final
file will be only at the usual compressed size.

This reverts commit 105de271.

Thomas Guillem authored May 03, 2021 and Hugo Beauzée-Luyssen committed May 04, 2021

cf. !68

The clock source selection depends on priv->b_can_pace_control but this
variable is only initialized from the input_thread_t after the demux is
opened. Programs and ES tracks can be created from the demux open
callback or midstream (from the demux callback). Therefore, we can't
handle the clock source selection after the program is created since
priv->b_can_pace_control might not be initialized. To fix this issue,
handle clock source selection when the first PCR is sent (from
ES_OUT_SET_PCR).

No functional changes.

Allow to attach the clock listener after the input clock is created.

No functional changes for now since only one master is created from
es_out.c (for now).

The input master clock has a higher priority than the ES master clock.
There can be one input master and one es master at a given time. In that
case, the ES master will behave as a slave clock.

This will allow to be more flexible from the es_out.c when creating
input and ES clocks.

Prince Gupta authored Apr 29, 2021 and Pierre Lamot committed May 03, 2021

Ref #25591

Prince Gupta authored Apr 23, 2021 and Pierre Lamot committed May 03, 2021

GridItem as a whole holds focus, no need to wrap it inside FocusScope

Prince Gupta authored Apr 09, 2021 and Pierre Lamot committed May 03, 2021

~20% ExpandGridView::layout performance improvement during scrolling