Hawktang

[hawktang]

Add usb type c support

[newAM]

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.

[hawktang]

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 <#171 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPJIZ4OKRJTS6TD7AVR573VKZXDPANCNFSM5WMYBQVA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[newAM]

set_input_source will allow an int to be used:

monitorcontrol/monitorcontrol/monitorcontrol.py

Line 403 in 9a31961

def set_input_source(self, value: Union[int, str, InputSource]):

get_input_source has an example of how to handle out-of-range values:

monitorcontrol/monitorcontrol/monitorcontrol.py

Lines 378 to 387 in 9a31961

	Handling out-of-spec inputs (observed for USB type-C inputs)::
	from monitorcontrol import get_monitors, InputSourceValueError
	for monitor in get_monitors():
	with monitor:
	try:
	print(monitor.get_input_source())
	except InputSourceValueError as e:
	print(e.value)

Does that cover your usecases?

[newAM]

Going to close in favor of #242 if I get a response from VESA.