Skip to content

refactor(magnifier): use shared ZOOM_INCREMENT_PRESETS const, adding 10% and 75% increments to settings UI - #2181

Open
tgrushka wants to merge 2 commits into
pop-os:masterfrom
dra11y:refactor-magnifier-zoom-increments
Open

tgrushka wants to merge 2 commits into
pop-os:masterfrom
dra11y:refactor-magnifier-zoom-increments

Conversation

@tgrushka

@tgrushka tgrushka commented Aug 28, 2026

Copy link
Copy Markdown

This PR:

  • Follows up on cosmic-comp PR #2616 and cosmic-comp issue #2615
  • Changes UI: Adds the two additional zoom increments: 10% and 75%, as approved by UX in #2615
  • Bumps cosmic-comp-config to 738e0b3 (merged #2616), not HEAD
    • Bumps libcosmic by side effect: 2a73fbc -> caec74c
    • Bump to later version left to maintainers' discretion
  • Replaces hard-coded zoom increments list in magnifier.rs with new const ZoomConfig::ZOOM_INCREMENT_PRESETS added in #2616

The version bump was produced using the following command (Cargo.lock was not hand-edited):

cargo update -p cosmic-comp-config --precise 738e0b312497dec066a611dc5ea98b75df39058e

just check-features and just test --all-features both green.
cargo clippy issues were pre-existing.

AI Assisted: Claude AI suggested (unsolicited) the updated line; I reviewed, understood, and approved it.


  • I have disclosed use of any AI generated code in my commit messages.
    • If you are using an LLM, and do not fully understand the changes it is making to the code base, do not create a PR.
    • In our experience, AI generated code often results in overly complex code that lacks enough context for a proper fix or feature inclusion. This results in considerably longer code reviews. Due to this, AI authored or partially authored PRs may be closed without comment.
  • I understand these changes in full and will be able to respond to review comments.
  • My change is accurately described in the commit message.
  • My contribution is tested and working as described.
  • I have read the Developer Certificate of Origin and certify my contribution under its conditions.

@leviport
leviport requested review from a team August 31, 2026 17:42
@leviport leviport self-assigned this Aug 31, 2026
leviport
leviport previously approved these changes Aug 31, 2026

@leviport leviport left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working as expected, and I'm not seeing any regressions with the magnifier. Thanks!

@leviport leviport removed their assignment Aug 31, 2026
wash2
wash2 previously approved these changes Aug 31, 2026
@mmstick

mmstick commented Sep 10, 2026

Copy link
Copy Markdown
Member

This PR needs to be rebased

**Changes UI:** Adds 10% and 75% zoom increments approved by UX in #2615.
Replaces hard-coded zoom increment list with new ZoomConfig::ZOOM_INCREMENT_PRESETS const.
Bumps cosmic-comp-config to 738e0b3 (merged #2616).
  - Side effect: Bumps libcosmic 2a73fbc to caec74c.
Follows up on #2616.

AI-assisted: unsolicited edit by Claude AI; reviewed and approved by author.
@tgrushka
tgrushka dismissed stale reviews from wash2 and leviport via c5230b1 September 10, 2026 19:31
@tgrushka
tgrushka force-pushed the refactor-magnifier-zoom-increments branch from 43e9b64 to c5230b1 Compare September 10, 2026 19:31
@tgrushka

Copy link
Copy Markdown
Author

@leviport , @wash2 - just rebased accepting your new Cargo.lock.

@tgrushka
tgrushka force-pushed the refactor-magnifier-zoom-increments branch from d2b717e to 296d3db Compare September 10, 2026 19:36
@tgrushka

Copy link
Copy Markdown
Author

Wait, that didn't work... had to run cargo update, hope that is OK.

cargo update -p cosmic-comp-config --precise 738e0b312497dec066a611dc5ea98b75df39058e
cargo update -p libcosmic --precise 2a73fbc0edfe1525381bf999e241d73def79b222
@tgrushka
tgrushka force-pushed the refactor-magnifier-zoom-increments branch from 296d3db to c1ba4fa Compare September 10, 2026 20:06
@tgrushka

Copy link
Copy Markdown
Author

Sorry guys, libcosmic HEAD broke things. Just pushed precise updates.

@leviport
leviport requested review from a team September 17, 2026 14:43
@mmstick

mmstick commented Sep 17, 2026

Copy link
Copy Markdown
Member

Needs to be rebased still. It shouldn't be necessary to update the Cargo.lock file.

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

Successfully merging this pull request may close these issues.

4 participants