monitorcontrol
monitorcontrol copied to clipboard
Hawktang
Add usb type c support
Can you point me to the specification that defines this value?
This isn't defined by the existing specifications and is vendor specific as far as I know; this value may not be the same on other Type-C monitors.
Hi, Alex,
As MCCS definitions above 0x12 are not assigned.
I only have 1 usb type c monitor at my hand. I am not sure if it is the value for other usb typc c monitors.
Anyway, if not so sure, could we add values about 0x12 in the enum list to enable select input by number or give users the way to customize the names?
[image: image.png] Peter Ze TANG (汤赜)
On Fri, May 20, 2022 at 12:56 AM Alex Martens @.***> wrote:
Can you point me to the specification that defines this value?
This isn't defined by the existing specifications and is vendor specific as far as I know; this value may not be the same on other Type-C monitors.
— Reply to this email directly, view it on GitHub https://github.com/newAM/monitorcontrol/pull/171#issuecomment-1131958333, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPJIZ4OKRJTS6TD7AVR573VKZXDPANCNFSM5WMYBQVA . You are receiving this because you authored the thread.Message ID: @.***>
set_input_source
will allow an int to be used:
https://github.com/newAM/monitorcontrol/blob/9a319610a963a92e8c7f93e06d88936e609b9c42/monitorcontrol/monitorcontrol.py#L403
get_input_source
has an example of how to handle out-of-range values:
https://github.com/newAM/monitorcontrol/blob/9a319610a963a92e8c7f93e06d88936e609b9c42/monitorcontrol/monitorcontrol.py#L378-L387
Does that cover your usecases?