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

Feature: remember multiple monitor configurations #175

Open
gpayer opened this issue Jun 19, 2024 · 3 comments
Open

Feature: remember multiple monitor configurations #175

gpayer opened this issue Jun 19, 2024 · 3 comments

Comments

@gpayer
Copy link

gpayer commented Jun 19, 2024

At the moment exactly one configuration can be saved. Unfortunately this quickly hits a limit if you regularly have different non-changing monitor configuration, e.g. a notebook with a home office configuration and a workplace configuration.

At home I have two monitors and the notebook is the third monitor on the right. At the office I have one big monitor and the notebook is on the left. Before I switched to Wayland autorandr took care of this, it saved configurations based on the monitor setup.

My feature idea: allow multiple configurations in cfg.yaml, each under a separate key representing the monitor configuration. This might either be a hash built from the monitor descriptions, or a unique key from a new section, where monitor configurations are explicitly saved.

One possible hash function would be to sort all monitor descriptions alphabetically and send them through a sha256 hasher.

@heyzec
Copy link

heyzec commented Jun 19, 2024

Would the potential profiles feature help with that? #83

@gpayer
Copy link
Author

gpayer commented Jun 19, 2024

@heyzec hm, there are similarities. The main difference is probably, that these proposed profiles are configured manually and the key for a specific configuration is calculated automatically.

@alex-courtis
Copy link
Owner

One possible hash function would be to sort all monitor descriptions alphabetically and send them through a sha256 hasher.

This is a good idea. For transparency/manual setup we could even just use the unhashed descriptions as the key.

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

No branches or pull requests

3 participants