[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Transparency -- take 2
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-09-29 14:09:37
[Download RAW message or body]

On Wed, 29 Sep 1999, Stefan Taferner wrote:
> On Wed, 29 Sep 1999, Mosfet wrote:
> > On Wed, 29 Sep 1999, Geert Jansen wrote:
> [...]
> > > I don't like this way. A better way (IMO) would be: kdesktop renders the
> > > backgroup (like it is doing now). It writes it to the root window's
> > > background and keeps it. It then publishes the pixmap ID to a property on
> > > the root window. The clients read this property and do a XCopyArea() to a
> > > QPixmap's handle(). A special class ("KBackgroundPixmap") will be provided 
> > > for the latter. 
> > 
> > I like this too and considered it (sharing the Pixmap handles across
> > applications). The problem: When KDesktop crashes all psudeo-transparent apps
> > will crash. You will need to check before each access and do something else if
> > the "server" is gone.
> 
> Are you sure?
> 
> I thought that the pixmaps are in the server, and if you do not free them they
> stay there. He wants to publish the ID, not the pointer. So it should work even
> in the case of a KDesktop crash.
> 

Nope. The resources will stay but the PixmapID will be invalid and you will get
a BadMatch error I believe (or Bad something, I forget which ;-).

> --Stefan
-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com

[prev in list] [next in list] [prev in thread] [next in thread]