feat(tile-snap): land 2/3 snap zones + DEV.md cleanup (v7.0.21)#5
Merged
Conversation
## Summary - Adds `LeftTwoThirds` / `RightTwoThirds` drop-zone markers to the macOS Tile Snap bottom row, centered at 12.5% and 87.5% with double width (`corner * 2`) so they read as distinct from the existing 1/3 markers - Full-width top "maximize" strip is untouched — most common snap target stays a full-width hit (Fitts' law) - Bumps to **v7.0.8** ## Why this layout Option discussion ended on bottom-row over top-row: - Bottom edge already speaks "horizontal anchor at X%" via the existing 25/50/75 third markers. 2/3 fits the same grammar. - Splitting the top edge into a narrow center "maximize" + side 2/3 markers would shrink the most-used snap target by ~70%. - Double width (100px vs 50px) keeps the markers visually distinct from the 1/3 row while sitting at the same `bottom_y` band. Hit-test math (1920px display): - LeftTwoThirds: x = 190..290 - LeftThird: x = 455..505 → ~165px gap, no overlap - BottomLeftQuarter: x = 0..50 (corners listed first → always win) ## Test plan - [x] `cargo test --lib` — 240 passed (4 new tests, no regressions) - [x] `npm test` — 115 passed - [ ] Manual: drag a window over the 12.5% / 87.5% markers and verify the left-2/3 / right-2/3 snap fires; verify 1/3 markers still work; verify corners still beat 2/3 markers 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>
# Conflicts: # src-tauri/tauri.conf.json
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
1 participant
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.
Summary
5a4daf0for v7.0.8 — never merged, ended up stranded on this branch.build_snap_zonesadds two wider drop targets at 12.5% and 87.5% along the bottom edge, mapped toLeftTwoThirds/RightTwoThirds. Corners still win priority. Covered bytest_build_snap_zones_bottom_two_thirdsand updated counts intest_build_snap_zones_single_display/_three_displays.3e2604c) that was already on this branch.mainat v7.0.20).origin/mainto bring the branch current.Why this PR exists
The original PR #12 was never opened on GitHub (or was deleted pre-merge) — the commit subject
(#12)is misleading. Main has been releasing v7.0.9 through v7.0.20 without these snap zones. This PR is purely a "land the dangling work" change, not new feature work.Test plan
cargo testinsrc-tauri/coverstest_build_snap_zones_bottom_two_thirds🤖 Generated with Claude Code