On Thursday, September 1st, 2022 at 13:36, Andrew Marshall
wrote:
> On Thu, 1 Sept 2022 at 12:01, Mikhail Gusarov wrote:
>
> >
> > In the described use-case compositor is most likely known and fixed.
>
> Yes, however can I guarantee that the output names will remain the same in
> the follow
For example, the advantage of having connection information is that I can
provide the following behaviour:
1. User assigns Camera 1 to DisplayPort1
2. User disconnects DisplayPort1
3. User connects a new monitor to DisplayPort1
4. Camera 1 is restored on the new monitor.
Regards,
Andrew.
On Th
On Thu, 1 Sept 2022 at 12:01, Mikhail Gusarov
wrote:
>
> In the described use-case compositor is most likely known and fixed.
>
>
Yes, however can I guarantee that the output names will remain the same in
the following scenarios -
* Rebooting of the system
* Disconnection and reconnection of dis
On 1 Sep 2022, at 12:26, Simon Ser wrote:
>> A medical device outputs a camera display to each of four monitors,
>> attached to display port connectors on the graphics card. There is a
>> 1:1 relationship between camera outputs and displays, and a UI allows
>> assigning a specific camera output to
On Thu Sep 1, 2022 at 6:23 AM EDT, Andrew Marshall wrote:
> No, but the information is available - so there must be a means of
> retrieving that information?
Not without a protocol.
> A medical device outputs a camera display to each of four monitors,
> attached to display port connectors on the
On Thursday, September 1st, 2022 at 12:23, Andrew Marshall
wrote:
> > Why do you need to fetch this information? What's your use-case?
>
> A medical device outputs a camera display to each of four monitors,
> attached to display port connectors on the graphics card. There is a
> 1:1 relationshi
On Thu, 1 Sept 2022 at 10:27, Simon Ser wrote:
> Hi,
>
> On Thursday, September 1st, 2022 at 11:23, Andrew Marshall <
> and...@algodynamic.com> wrote:
>
> > I have an application that requires the equivalent of the
> > `ConnectorNumber` and `ConnectorType` properties that are available
> > in the
Hi,
On Thursday, September 1st, 2022 at 11:23, Andrew Marshall
wrote:
> I have an application that requires the equivalent of the
> `ConnectorNumber` and `ConnectorType` properties that are available
> in the RandR protocol in X11 (see
> https://github.com/freedesktop/xorg-xorgproto/blob/master
I have an application that requires the equivalent of the `ConnectorNumber`
and `ConnectorType` properties that are available in the RandR protocol in
X11 (see
https://github.com/freedesktop/xorg-xorgproto/blob/master/randrproto.txt)
For various reasons related to multi-monitor setups and refresh
