Am 2014-01-10 17:10, schrieb Pekka Paalanen:
Well, if the user wants to capture it like that, maybe she rather takes
a shot of the whole desktop?
Maybe I'm just weird, but when I think about capturing a single window,
I really think about the window contents, not how it is presented on
screen. If I want how the thing is presented on screen, I capture the
screen and maybe crop afterwards.
I find it annoying, that I have to raise a window to take a shot of
it without obscuring it with other windows.
Completely agree with you. Recording a window instead of the whole
screen is something I really, really want to do.
> In your proposition, how do you define what is part of the window or
> not? It needs to relate to the protocol objects somehow.
I assumed it would be impossible (or at least very impractical) to
capture tooltips and menus as part of a window. I mean, what if the
window is transformed and the tooltips are not? I wanted to avoid the
issue entirely by simply recording the screen as-is, by choosing a
rectangle on the screen based on x/y/w/h. Do you think it is realistic
to require that all compositors implement the complex logic to capture
and follow a single window, without transformations, but with support
for tooltips and menus? I fear that most compositors won't implement
it at all, and if they do, it will likely be buggy because it hasn't
seen enough testing.
It could be optional. But sure, it will be very complicated, and that
is what "window capturing" means to me in the broadest sense. Maybe we
should forget window capturing.
I disagree. It will be very complicate, but we should at least try it.
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
