GTK2 font settings

[Lubos Lunak]

On Wednesday 09 of April 2003 13:51, Stephan Kulow wrote:
> On Wednesday 09 April 2003 12:38, Lubos Lunak wrote:
> > On Friday 28 of March 2003 19:25, Lubos Lunak wrote:
> > > On Friday 28 of March 2003 18:58, David Faure wrote:
> > > > On Friday 28 March 2003 18:28, Havoc Pennington wrote:
> > > > > On Fri, Mar 28, 2003 at 11:02:39AM +0100, Craig Drummond wrote:
> > > > > > Why does the gnome-settings-daemon insist on owning the desktop?
> > > > >
> > > > > gnome-settings-daemon is similar to krdb - basically what it does
> > > > > is propagate gconf settings out to lots of non-gconf stuff. So it
> > > > > sets some X resources, grabs some X keys, sets XKB properties, sets
> > > > > the background, all this type of thing.
> > > > >
> > > > > I don't think it owns the desktop
> > > >
> > > > Check the XKillClient call at the end of
> > > > http://bugs.kde.org/show_bug.cgi?id=31619
> > >
> > >  Maybe kdesktop should use a separate XServer connection for setting
> > > these pixmaps, use XSetCloseDownMode() and close this separete
> > > connection. That would prevent others from killing it. It's maybe even
> > > part of the "spec" for setting the background pixmaps for
> > > englightenment that the old pixmap should be killed :-/.
> >
> >  Just for the recond: After having completed a solution that managed to
> > survive that XKillClient(), I found out that this was kdesktop bug after
> > all - whoever copied it from Esetroot apparently didn't realize that
> > kdesktop shouldn't set ESETROOT_PMAP_ID at all. So it doesn't now.
>
> I think, this was there so that apps like xchat can find the backgroup
> pixmap to get a transparent background.

 I tested it with Eterm, and it still works. From Eterm ChangeLog:

        Just to document what we came up with....  Esetroot sets the
        _XROOTPMAP_ID property as always, but now it sets a companion property
        as well, ESETROOT_PMAP_ID.  Both are set to the same pixmap ID.  When
        Esetroot runs, it checks to see if _XROOTPMAP_ID == ESETROOT_PMAP_ID,
        and if so, it knows that it set the pixmap itself and can safely do
        an XKillClient() on it.  If they are not equal, calling XKillClient()
        would kill the application which did set it, most likely a window
        manager like Enlightenment or the patched versions of AfterStep or
        WindowMaker.

 Since kdesktop cleans up after itself, just _XROOTPMAP_ID is enough.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/