Skip to content
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

Selection box doesn't dissapear quickly enough #252

Closed
Brottweiler opened this issue Nov 21, 2014 · 2 comments
Closed

Selection box doesn't dissapear quickly enough #252

Brottweiler opened this issue Nov 21, 2014 · 2 comments

Comments

@Brottweiler
Copy link
Contributor

Using compton and making a selection with scrot -s, or in my case escrotum -s, you get a slightly different selection box, that's not fully transparent but see-through gray box. Not sure how to describe it, but you should know what I mean.

The issue is that when making a screenshot using escrotum -s, this gray box doesn't dissapear fast enough, so (e)scrot(um) ends up including it in the screenshot.

Sometimes it's the entire picture that's grey, and rarely it ends up beeing like half the picture for some reason.

I am unsure if this is a compton issue or not, but I think it is.

Example:

@richardgv
Copy link
Collaborator

Regarding scrot:

scrot paints a rectangle on the root window, and as stated in #226 (comment) , compton doesn't always work correctly with other programs that attempts to draw things onto the root window. However in the case of scrot, I have never encountered corruptions on the screenshot taken due to the problem. Try switching backend and/or flipping --paint-on-overlay might help, should you find a problem here.

Regarding escrotum:

Escrotum creates a window and doesn't have the issue of scrot. It takes the screenshot 100ms after you make the selection (unlike scrot, which places the delay after selection, heh).

  1. If you have fading enabled, try disabling it globally or disabling it on the specific window with --fade-exclude 'class_g = "Escrotum"'.

  2. If the problem is not caused by fading... Might be something like Compton keeps window active during screenshots #208? In which case I would recommend you to:

    1. Tell us about your hardware, driver (+ version), and versions of related packages.
    2. Check if the problem exists with compton --config /dev/null.
    3. Check if you see performance issues when playing videos or playing games.
    4. Check if the delay occurs when you close/unmap other windows.
    5. Check if changing backend or flipping --paint-on-overlay helps.
    6. Check if --benchmark 100000 changes anything. Measure the performance using the method described in the performance guide
    7. Check whether it happens with other screenshot takers.
    8. Try my other suggestions in Compton keeps window active during screenshots #208.
  3. You could increase the delay in escrotum, as a workaround. On line 215 in escrotum/main.py (as in version 0.2.1):

    gobject.timeout_add(100, self.screenshot)

    See the "100"?

@Brottweiler
Copy link
Contributor Author

If you have fading enabled, try disabling it globally or disabling it on the specific window with --fade-exclude 'class_g = "Escrotum"'.

This was the issue, I added

fade-exclude = [ 
    "name = 'Screenshot'",
    "class_g = 'Escrotum'"
];

to my compton.conf and it solved the issue. Thanks!

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

No branches or pull requests

2 participants