Repository navigation
grimblast: support cursor in frozen area capture - #196
Conversation
fufexan
left a comment
There was a problem hiding this comment.
Why have CURSOR and CAPTURE_CURSOR? Can't we use one variable?
Also, how will this work with existing hyprpicker versions?
|
@fufexan Sry for the late reply
Woops, we could use CURSOR for both yeah.
Maybe I should do a check for the |
Sure, can be done. |
|
@fufexan alrighty |
|
@fufexan hi, wondering if we could get this merged |
|
Oops, I did not see your comment in may. We can, but it needs another rebase. |
19baa12 to
8cf5e24
Compare
|
@fufexan That's alright! Rebased and also fixed clicking a window with |
|
My bad, I merged something and the changelog now conflicts. |
33612de to
d8613eb
Compare
|
Thanks! |
Description of changes
Allow
grimblast --freeze --cursor ... areanow that hyprpicker can include the cursor in its frozen screencopy.Fixes #92 (with the caveat that it only works with hardware cursors, software cursors still borked).
Depends on hyprwm/hyprpicker#156.
For new programs
For changes
Example: (notice there's no double cursor)