| Age | Commit message (Collapse) | Author |
|---|
|
Presentation subsurface fix, popup unconstrain resize fix, cursor shape fix, refactors.
|
|
This backs out commit 763cd564e32932e5f05b983c93328300f396216b.
There are graphical glitches and a panic.
|
|
|
|
This both avoids sending frame callbacks to surfaces invisible on the offscreen
(fixing Firefox with subsurface compositing in the process), and fixes
searching for split popups during the resize animation.
|
|
Now that offscreen does damage tracking, we can reasonably do this. Note this
only affects full-tile opacity, not window opacity.
|
|
|
|
This is the second part of the damage equation: now the offscreen element
itself reports correct damage, so partial redraws to the texture don't cause
full redraws of the texture element itself.
|
|
Does not yet signal the damage outside, but does skip rerendering if there was
no damage.
|
|
Don't recreate it unless the size changes. This lays the groundwork for also
tracking damage in the future.
|
|
|
|
|
|
Supports fractional texture scale + has some getters.
|
|
|
|
|
|
* Implement wlr-screencopy
* Finish the implementation
Lots of changes, mainly to fix transform handling. Turns out, grim
expects transformed buffers and untransforms them by itself using info
from wl_output. This means that render helpers needed to learn how to
actually render transformed buffers.
Also, it meant that y_invert is no longer needed.
Next, moved the rendering to the Screencopy frame handler. Turns out,
copy() is more or less expected to return immediately, whereas
copy_with_damage() is expected to wait until the next VBlank. At least
that's the intent I parse reading the protocol.
Finally, brought the version from 3 down to 1, because
copy_with_damage() will need bigger changes. Grim still works, others
not really, mainly because they bind v3 unnecessarily, even if they
don't use the damage request.
---------
Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>
|
|
|
|
|
|
|
