Use output display or region geometry to record #1920
Merged
+3
−2
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.
Adding this PR as a fix for #1858
The identified issue is when using the hyprctl bindings from default/hypr/bindings/utilities.conf
The call to omarchy-cmd-screenrecord differentiates output versus region as the first parameter used. A conditional is used to identify if the bash script caller is expecting a region or a display output for screen recording. The region handled this as a geometry, first calling slurp, and passing it to wf-recorder or wf-screenrec. The display was calling wf-recorder or wf-screenrec without any geometry flags which had an unexpected response, always attempting to capture the region of the screen allowing no way to capture solely the display.
Details for reference
wf-recorder usage
slurp usage reference