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
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: