-
-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transparent-clipping and screenshot tools #663
Comments
Ran into the same issue when using |
I have this script which is working. I use my graphics card to run Anyways, my solution at the moment is to kill picom; take the shot; run picom again. I believe this is sensible and in accord to UNIX philosophy. This way you are composing scripts and programs, instead of trying to make picom do everything. #!/bin/sh
# This is bound to Shift+PrintScreen by default, requires maim. It lets you
# choose the kind of screenshot to take, including copying the image or even
# highlighting an area to copy. scrotcucks on suicidewatch right now.
kill $(pidof picom)
case "$(printf "a selected area\\ncurrent window\\nfull screen\\na selected area
(copy)\\ncurrent window (copy)\\nfull screen (copy)" | dmenu -l 6 -i -p
"Screenshot which area?")" in
"a selected area") maim -s pic-selected-"$(date '+%y%m%d-%H%M-%S').png" ;;
"current window") maim -i "$(xdotool getactivewindow)" pic-window-"$(date '+
%y%m%d-%H%M-%S').png" ;;
"full screen") maim pic-full-"$(date '+%y%m%d-%H%M-%S').png" ;;
"a selected area (copy)") maim -s | xclip -selection clipboard -t image/png ;;
"current window (copy)") maim -i "$(xdotool getactivewindow)" | xclip -
selection clipboard -t image/png ;;
"full screen (copy)") maim | xclip -selection clipboard -t image/png ;;
esac
prime-run $(picom --experimental-backends) Hope it helps. |
If this satisfies you, please awnser. So, we can close the issue (picom has a lot of them open right now, and most of them landing in composability-problems, instead of picom-working-problem). |
I haven't run your script but looking at it it seems like the screenshots won't show the effects of picom which is a significant caveat. The goal here is not to make picom do everything and excluding selected windows from |
I'm closing this since it seems like it's fixed now. At least it doesn't break anymore on my system neither with flameshot nor maim anymore (using latest master build). |
@DarkReaper231 there is a pull request: #738 |
Would you mind merging? Having self built packages in arch can be quite tricky when you for example release new bug fixes. |
@DarkReaper231 thanks for confirming! |
If you enable transparent-clipping, screenshot tools are making whole screen transparent. You can test it via either
flameshot
ormaim
. I was expecting that excluding focus + setting transparency to 100 specifically for it to work, but sadly it didn't.Platform
Linux amd64 (NixOS 21.05)
GPU, drivers, and screen setup
Nothing special:
Environment
Awesomewm latest
picom version
v8.2
Diagnostics
Configuration:
Configuration file
Steps of reproduction
picom --experimental-backends --transparent-clipping
maim
orflameshot gui
Expected behavior
A way to ignore screenshot "overlay" so we can see what we want to select on screenshot tool
Current Behavior
Overlay makes everything transparent
The text was updated successfully, but these errors were encountered: