Skip to content

grimblast: support cursor in frozen area capture#196

Open
shovel-kun wants to merge 1 commit intohyprwm:mainfrom
shovel-kun:grimblast-cursor-freeze-area
Open

grimblast: support cursor in frozen area capture#196
shovel-kun wants to merge 1 commit intohyprwm:mainfrom
shovel-kun:grimblast-cursor-freeze-area

Conversation

@shovel-kun
Copy link
Copy Markdown

Description of changes

Allow grimblast --freeze --cursor ... area now 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

    • Add the program to the README table, with yourself as the maintainer
    • Add a README for the program itself
    • Add Makefile (and Nix derivation optionally, otherwise @fufexan will do it)
    • If the program is a script, add it to the CI checks matrix
  • For changes

    • Add changes to the CHANGELOG
    • Reflect your changes in the man pages (if they exist)

Example: (notice there's no double cursor)

image

Copy link
Copy Markdown
Member

@fufexan fufexan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why have CURSOR and CAPTURE_CURSOR? Can't we use one variable?

Also, how will this work with existing hyprpicker versions?

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.

--cursor flag doesn't work in grimblast

2 participants