The current check to grab a monitor's existing settings from the config.json file in display.py try and match by name - which is a combo of the GDK-provided brand and model info. Somebody with identical models of monitor will just load the first found block with that name twice.
I got lucky that my two monitors are from two different years (and therefore different models), but capturing some other data to help us disambiguate would be good.
I know pyEDID has tools to grab monitor EDID info including serial number, which could help.
Another approach would be to see if there's an existing identical (or near-identical?) match for id/geometry/orientation in the case of multiple displays with the same name.
The current check to grab a monitor's existing settings from the config.json file in display.py try and match by name - which is a combo of the GDK-provided brand and model info. Somebody with identical models of monitor will just load the first found block with that name twice.
I got lucky that my two monitors are from two different years (and therefore different models), but capturing some other data to help us disambiguate would be good.
I know pyEDID has tools to grab monitor EDID info including serial number, which could help.
Another approach would be to see if there's an existing identical (or near-identical?) match for id/geometry/orientation in the case of multiple displays with the same name.