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

List:       kde-core-devel
Subject:    Re: More on Kasbar X problem - is extension proxy to blame?
From:       m_elter () t-online ! de (Matthias Elter)
Date:       2001-07-18 8:30:54
[Download RAW message or body]

On Wednesday 18 July 2001 00:29, Richard Moore wrote:
> On Tuesday 17 July 2001 20:21, Matthias Elter wrote:
> > On Tuesday 17 July 2001 18:31, Richard Moore wrote:
> > > When adding and removing Kasbar lots (to test the various things) I
> > > noticed that I was getting some BadDrawable errors from X when the
> > > extension is removed. Looking deeper this seems to be an extension
> > > proxy issue as the same thing happens with the external panel. Could
> > > this be causing your troubles David? The error says it comes from
> > > Kicker (as you reported) however my kasbar is definitely running in its
> > > own
> > > extensionproxy process. This seems to be some attempt by kicker to
> > > access the extensionproxy after it has been destroyed (perhaps
> > > something to do with the work area handling?).
> >
> > Perhaps some QXEmbed issue.
>
> Ok, I updated from cvs and this error has gone away. This could be just
> because some timing issue has changed, or it could really be fixed - no way
> to tell. :-(
>
> I've also added some extra checks around a couple of places kasbar might
> possibly be triggering the issue David found, though I'm still not 100%
> convinced that this is a kasbar issue rather than a more general issue for
> extensions. I'll also try to get some KRootPixmap improvements written over
> the next couple of days that will let me replace the current transparency
> code in kasbar with something less convoluted.

I don't think so, as external applets and extensions share pretty much the 
same crucial code (embedding and dcop).

Matthias

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