From: Jacopo De Simoi <wilderkde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: New window pixmap initialization
Date: Tue, 8 Mar 2011 22:30:20 +0100 [thread overview]
Message-ID: <201103082230.20866.wilderkde@gmail.com> (raw)
In-Reply-To: <201103041034.09766.wilderkde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Nevermind, I found out that it was a bizarre strategy of Qt for some specific window types
apologies for the noise
_J
> Hello nouveau devs
>
> I'd like some informations on the pixmap initialization for a new window in
> a (xrender) composited setting; I'm currently trying to improve the xrender backend of
> kwin (i.e. kde composited window manager) and I'm facing some issues which might
> or might not be driver related.
>
> From what it seems, when a new window is created with geometry (x y w h)
> the pixmap is first initialized with the content of the screen in the rect (x y w h),
> is this correct?
>
> This actually is causing glitches with effects that animate the appearance of the given window
> by some kind of motion, since one can see for a split second a portion of screen moving for no reason
> and afterwards the new window appearing (as soon as it has been first painted).
>
> Imvho, if an argb window is created, it would be much much cleaner to init its pixmap with a fully
> transparent color; trying to implement this in the wm is kind of weird; on the other hand
> I got pretty quickly lost examining ddx code, so I have a few questions:
>
> 1· Is first pixmap creation in a composited setting driver dependent?
> 2· I assume that upon creation the contents of the pixmap should actually be undefined
> and are init'd like I said for purely convenience reasons; is this correct? is there anything in the specs about that
> which I did not see?
> 3· Would it be possible for the nouveau driver to implement the alternate initialization strategy for argb windows?
> Does the new strategy make sense to you?
> 4· I'd be happy to provide a patch for point 3, provided that somebody helps me out with finding the right place
> for it;
>
> Thanks a lot;
> __J
>
> P.S. I'm always on IRC, nick wilder
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
>
prev parent reply other threads:[~2011-03-08 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 9:34 New window pixmap initialization Jacopo De Simoi
[not found] ` <201103041034.09766.wilderkde-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-08 21:30 ` Jacopo De Simoi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201103082230.20866.wilderkde@gmail.com \
--to=wilderkde-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.