feat: add collaboration settings and host policy sync - #18
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Co-op setup previously required CLI commands, guest notification and strict behavior could conflict with local configuration, and a guest's zero-second resume input could race the host deadline. Fixed-width overlay content could also overflow smaller monitors.
Impact
Users can manage rooms entirely from the GTK settings window. Co-op participants follow one coordination policy while retaining local opacity, monitor, messages, sound, and other presentation choices. The settings poll uses IPC rather than spawning recurring processes, and co-op remains inactive-cost-free when disabled.
Validation
cargo test --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo build --locked --release --workspace