Signed-off-by: Sebastian Krzyszkowiak
---
stable/xdg-shell/xdg-shell.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml
index e259a1f..2e420c6 100644
--- a/stable/xdg-shell/xdg-shell.xml
+++ b/stable/xdg-shell/xd
On 11/5/18 7:43 AM, Simon Ser wrote:
> On Monday, November 5, 2018 11:07 AM, Pekka Paalanen
> wrote:
>> How about writing what Derek said: that the old damage request may be
>> unoptimal rather than deprecated.
>>
>> I don't like "deprecated" because to me it implies that this request
>> will be
On 11/5/18 7:57 AM, Simon Ser wrote:
> This commit makes wl_surface.damage_buffer preferred over wl_surface.damage.
> wl_surface.damage can be implemented in a non-optimal way by the compositor
> (e.g. by always damaging the whole buffer).
>
> Having two requests makes it complicated for the compo
On Monday, November 5, 2018 10:50 AM, Alexandros Frantzis
wrote:
> On Sat, Nov 03, 2018 at 02:44:53PM +, Simon Ser wrote:
>
> Hi Simon,
>
> > > > > + Explicit synchronization is guaranteed to be supported only
> > > > > for buffers
> > > > > + created with any version of the zwp_li
On Mon, 05 Nov 2018 13:57:00 +
Simon Ser wrote:
> This commit makes wl_surface.damage_buffer preferred over wl_surface.damage.
> wl_surface.damage can be implemented in a non-optimal way by the compositor
> (e.g. by always damaging the whole buffer).
>
> Having two requests makes it complica
This commit makes wl_surface.damage_buffer preferred over wl_surface.damage.
wl_surface.damage can be implemented in a non-optimal way by the compositor
(e.g. by always damaging the whole buffer).
Having two requests makes it complicated for the compositor to handle damage,
making it necessary to
On Monday, November 5, 2018 11:07 AM, Pekka Paalanen
wrote:
> How about writing what Derek said: that the old damage request may be
> unoptimal rather than deprecated.
>
> I don't like "deprecated" because to me it implies that this request
> will be removed (i.e. can be left unimplemented) some
On Mon, 05 Nov 2018 08:58:46 +
Simon Ser wrote:
> On Monday, November 5, 2018 9:44 AM, Pekka Paalanen
> wrote:
> > Hi,
> >
> > what good does this do, when no compositor can ever stop implementing it?
> >
> > I'm ok with adding a note that clients might have easier time using
> > damage_buf
On Sat, Nov 03, 2018 at 02:44:53PM +, Simon Ser wrote:
Hi Simon,
> > > > + Explicit synchronization is guaranteed to be supported only for
> > > > buffers
> > > > + created with any version of the zwp_linux_dmabuf buffer factory.
> > >
> > > I think we can drop the "z" prefix here.
Hi Valentino
Am 04.11.18 um 12:59 schrieb Valentino Bocchino:
> Hi,
> I’m Valentino, I come from Italy and I’m 14 years old. I am really interested
> in learning programming languages and I thought that asking the Wayland team
> how they built Wayland could be a great idea. I don’t carry any kin
On Monday, November 5, 2018 9:44 AM, Pekka Paalanen wrote:
> Hi,
>
> what good does this do, when no compositor can ever stop implementing it?
>
> I'm ok with adding a note that clients might have easier time using
> damage_buffer, but I don't see anything that would allow compositors to
> do othe
On Fri, 02 Nov 2018 18:38:10 +
Simon Ser wrote:
> On Friday, November 2, 2018 9:53 AM, Pekka Paalanen
> wrote:
> > > I think we want another event here, to group sets of modifiers
> > > together by preference.
> > >
> > > For example, say the surface could be directly scanned out, but only
On Sun, 04 Nov 2018 08:38:16 +
Simon Ser wrote:
> This commit deprecates wl_surface.damage in favor of wl_surface.damage_buffer.
>
> Having two requests makes it complicated for the compositor to handle damage,
> making it necessary to transform one into the other's coordinates.
>
> Moreove
13 matches
Mail list logo