Repository navigation
Conversation
Actions started the instant Enter was pressed, while the launcher layer was still on screen (fade-out). Screenshot actions froze and captured the screen with the launcher's borders still visible. Delay the command by 0.3s so the layer is gone first. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Problem
Running Screenshot (or any Omarchy action) from omacast starts the command the moment Enter is pressed, while the launcher layer is still on screen (Hyprland's layer fade-out). `omarchy-capture-screenshot` freezes the screen and captures it, so the launcher's borders and half-faded rows end up in the screenshot.
Fix
`Backend.runShell` now runs the command as `sleep 0.3; `, giving the layer time to unmap. Summon actions (`omarchy-shell shell summon …`) are unchanged.
Testing
The delay applies to every non-summon action, not just screenshots. A tighter alternative would be waiting for the `omacast` layer to disappear from `hyprctl layers` instead of a fixed delay; happy to switch if you prefer.
🤖 Generated with Claude Code