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.

Sign up for GitHub

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

Jump to bottom

config/output: Search for output config fallbacks #8095

Merged
merged 2 commits into from May 2, 2024
Merged

config/output: Search for output config fallbacks #8095

merged 2 commits into from May 2, 2024

Commits on May 2, 2024

  1. config/output: Search for output config fallbacks 

    The original sway output config implementation enabled one output at a
time, testing modes, render formats and VRR support as it went along.
While this sort of fallback is easy to do, it has the downside of not
considering the effect of neighbor outputs on the configuration
viability.

With backend-wide commits, we can now better consider the effect of
neighbor outputs, but to handle the fact that we commit all outputs at
once we need to perform a more elaborate search of viable
configurations.

Implement a recursive configuration search for when the primary
configuration failed to apply.
    @kennylevinsen
    kennylevinsen committed May 2, 2024
    Configuration menu
    Copy the full SHA
    5db0c9b View commit details
    Browse the repository at this point in the history

  2. config/output: Print output state during tests 

    Instead of having each search function print its various test decisions,
print the full state at the end of every search. This makes it much
clearer what state a particular test includes.
    @kennylevinsen
    kennylevinsen committed May 2, 2024
    Configuration menu
    Copy the full SHA
    b341cd4 View commit details
    Browse the repository at this point in the history