Repository navigation
Show the launcher on outputs scaled below 1 - #101
Merged
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.
Summary
On an output scaled below 1, the launcher maps and grabs the keyboard but never draws: Qt keeps
devicePixelRatioat 1 while Hyprland reports the real scale, socontentReadynever holds.Evidence
Logged on a 1920x1080 HDMI output at scale 0.8 (Omarchy 4.5, Hyprland 0.56), 500 ms after
omacast:toggle:The same log on the 1.6 laptop panel reads
devicePixelRatio=1.6 monitor.scale=1.6, and it opens there.New
tests/content-ready.test.jsevaluates thecontentReadybinding fromui/LauncherWindow.qmlin node:✖ content is revealed on an output scaled below 1(pass 2, fail 1)After:
node --test tests/*.test.js: 187 pass, 0 fail, 3 skipped (live QML runner);omarchy plugin validate .passes.Merge Danger
Door: two-way
One expression in a binding; reverting the commit restores the old behaviour.
Blast Radius: sub-1x outputs
Outputs at scale ≥ 1 compute exactly as before. On outputs below 1 the card is now revealed instead of staying transparent.