Skip to content

feat: filter layouts by minimum monitor resolution#546

Open
thameem-abbas wants to merge 1 commit intodomferr:mainfrom
thameem-abbas:feat/min-resolution-layout-filtering
Open

feat: filter layouts by minimum monitor resolution#546
thameem-abbas wants to merge 1 commit intodomferr:mainfrom
thameem-abbas:feat/min-resolution-layout-filtering

Conversation

@thameem-abbas
Copy link
Copy Markdown

Auto-hide layouts on monitors too small to render their tiles usably. Each tile's pixel width is checked against a configurable threshold (default 300px). Layouts can also set explicit minimumMonitorResolution.

  • Add MinimumResolution interface and optional field to Layout class
  • Add minimum-tile-width-threshold GSettings key and prefs spin button
  • Add centralized filtering utility (layoutFiltering.ts)
  • Add GlobalState.getLayoutsForMonitor() for per-monitor filtered lists
  • Update indicator menu, layout switcher, snap assistant to use filtered layouts
  • Validate selected layouts against monitor suitability on monitor change
  • Fix npm install: add overrides for unpublished @girs/mtk-17@rc.4

Tested on GNOME 49.2
No access to GNOME <= 44

Auto-hide layouts on monitors too small to render their tiles usably.
Each tile's pixel width is checked against a configurable threshold
(default 300px). Layouts can also set explicit minimumMonitorResolution.

- Add MinimumResolution interface and optional field to Layout class
- Add minimum-tile-width-threshold GSettings key and prefs spin button
- Add centralized filtering utility (layoutFiltering.ts)
- Add GlobalState.getLayoutsForMonitor() for per-monitor filtered lists
- Update indicator menu, layout switcher, snap assistant to use filtered layouts
- Validate selected layouts against monitor suitability on monitor change
- Fix npm install: add overrides for unpublished @girs/mtk-17@rc.4

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@thameem-abbas
Copy link
Copy Markdown
Author

thameem-abbas commented Apr 21, 2026

Still have not gotten a chance to test the other features. Also considering if we should do a better job with auto detecting defaults rather than setting an arbitrary value of 300

@thameem-abbas thameem-abbas marked this pull request as ready for review May 4, 2026 11:33
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.

1 participant