You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BetterDisplay could auto detect any conflicts and offer optimal decision if any exists.
Procedure could look like this:
Find [vendor, product] vector conflicts. If none exists, use product id and go to 3. Otherwise go to 2.
Find [year, week] vector conflicts amongst [vendor, product] conflicts. If none exists, use manufacture date and go to 3. Otherwise report the need of EDID change.
Find existing overrides conflicts against a new one to avoid overwrites. If none exists, create a new one. Otherwise report the need of EDID change.
This procedure is valid as long as macOS takes product id precedence over manufacturing date, which is currently true for Sonoma (as tested on display powering up with fs_usage in #2749).
I think I'll go with creating vendor/product as default but have a minor option to use year/week instead but leave it to an user decision. Either way, the app should warn the user with potential conflict for existing known displays with possibly a suggestion - #2809
It is always possible for a conflicting display to be connected later and many displays don't have the year/week data filled properly which can create even more conflicts going forward as it can create a vendor level confusion (if a vendor habitually does not properly supply manufacturing date data). Vendor and model numbers are universally properly supplied.
I think the need for renaming exists only in fixed multi display environment for quick identity, where exchanging is rare (in case of faulty display replacement or upgrade) and thus rather permanent. In any other case I doubt that anyone would bother to do it. It seems to me the same applies to other display params that can be changed using overrides.
Related the discussion here: #2749 (reply in thread)
The text was updated successfully, but these errors were encountered: