[GH-ISSUE #113] Create an intelligent algorithm for saving identified monitors to decrease the time for searching #83

New issue

Closed

opened 2026-05-05 05:00:08 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:00:08 -06:00

Owner

Originally created by @MHX792 on GitHub (Aug 18, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/113

One of my monitors takes way too long to be identified, while others get identified really quick. It would be great, if you could maintain an array of already identified monitors. The next time a monitor gets attached, first search this array. If unsuccessful, search the whole list.

Thanks

Originally created by @MHX792 on GitHub (Aug 18, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/113 One of my monitors takes way too long to be identified, while others get identified really quick. It would be great, if you could maintain an array of already identified monitors. The next time a monitor gets attached, first search this array. If unsuccessful, search the whole list. Thanks

gitea-mirror

2026-05-05 05:00:08 -06:00

closed this issue
added the
Status: Abandoned
label

gitea-mirror commented

2026-05-05 05:00:17 -06:00

Author

Owner

@JoniVR commented on GitHub (Aug 27, 2019):

It's a nice idea but I'm not sure if that could work given how ddc works (not too sure about the details), in the meantime, once the advanced prefs panel is released, I'd recommend trying the longerDelay option for that specific display, that might fix it taking so long to identify.

Also, setting Polling Mode/Count really low for that specific display will also work.. in case it can't read the values it will use the last saved ones.

@JoniVR commented on GitHub (Aug 27, 2019): It's a nice idea but I'm not sure if that could work given how ddc works (not too sure about the details), in the meantime, once the advanced prefs panel is released, I'd recommend trying the `longerDelay` option for that specific display, that might fix it taking so long to identify. Also, setting Polling Mode/Count really low for that specific display will also work.. in case it can't read the values it will use the last saved ones.

gitea-mirror commented

2026-05-05 05:00:20 -06:00

Author

Owner

@stale[bot] commented on GitHub (Aug 3, 2021):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 3, 2021): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror referenced this issue

2026-05-05 07:02:51 -06:00

[PR #83] [MERGED] Update DDC.swift. #1036