Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add week/year of manufacture based way to save display configuration edit (override) as an option #2832

Open
waydabber opened this issue Apr 3, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@waydabber
Copy link
Owner

Related the discussion here: #2749 (reply in thread)

@waydabber waydabber added the enhancement New feature or request label Apr 3, 2024
@KrzysztofPrzygoda
Copy link

KrzysztofPrzygoda commented Apr 3, 2024

BetterDisplay could auto detect any conflicts and offer optimal decision if any exists.

Procedure could look like this:

  1. Find [vendor, product] vector conflicts. If none exists, use product id and go to 3. Otherwise go to 2.
  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.
  3. 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).

@waydabber
Copy link
Owner Author

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.

@KrzysztofPrzygoda
Copy link

KrzysztofPrzygoda commented Apr 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants