Email or username:

Password:

Forgot your password?
4 comments
Tobias Bernard

@drq @neilsardesai We already take screenshots of all windows for the per-window screenshots, so this is actually feasible lol

I guess what you'd have to do is do a separate wallpaper+top panel screenshot, and then have all the layers in a single file that supports this (maybe SVG?).

Lyyn ☮️

@tbernard @drq @neilsardesai I thought that compositors should optimize drawing, for example, windows covered by other windows, or even parts of windows which are covered. In this case it would be impossible to get all window's contents. Or we could force the applications to draw just for the screenshot?

Val Packett

@lyyn@mastodon.ml @tbernard@mastodon.social @drq@mastodon.ml @neilsardesai@mastodon.social it would be impossible without a compositor, in an old school xorg setup / windows pre-aero etc. Any compositor has access to all the buffers submitted by clients, that's how it… well… composes them. Of course drawing is very optimized; there's even damage tracking to only redraw little parts of the windows that changed. But such a "screenshot" functionality doesn't have anything to do with what's drawn on screen, it would just access the sources of what was composited onto the screen.

I've actually built that (without assembling into a layered image editor file…) for Weston way back when haha

@lyyn@mastodon.ml @tbernard@mastodon.social @drq@mastodon.ml @neilsardesai@mastodon.social it would be impossible without a compositor, in an old school xorg setup / windows pre-aero etc. Any compositor has access to all the buffers submitted by clients, that's how it… well… composes them. Of course drawing is very optimized; there's even damage tracking to only redraw little parts of the windows that changed. But such a "screenshot" functionality doesn't have anything to do with what's drawn on...

Go Up