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

List:       kwrite-devel
Subject:    Re: X-KDE-PluginInfo-Depends not working for KTextEditor Plugins?
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2008-12-22 13:54:36
Message-ID: 20081222135434.GD23974 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]

On 22.12.08 14:12:09, Milian Wolff wrote:
> Here a follow up to this issue:
> 
> I severely doubt the X-KDE-PluginInfo-Depends is taken into account when 
> loading or deleting KTextEditor plugins. Attached you'll find two very simple 
> KTextEditorPlugins, parent and child. Obviously child depends on parent. The 
> Plugin configuration screen works fine, i.e. when I enable child it makes sure 
> parent gets enabled as well. So far so good.
> 
> Now enable both, apply and quit kwrite. You'll notice some debug output on the 
> console. For me it looks like this:
> 
> > $ kwrite                                                    
> > kwrite(12991) ParentPlugin::ParentPlugin: Parent Plugin setup.                    \
> >  kwrite(12991) ChildPlugin::ChildPlugin: Child Plugin setup, Parent should 
> have been setup already!       
> > kwrite(12991) ParentPlugin::~ParentPlugin: Parent Plugin destroyed!               \
> >  kwrite(12991) ChildPlugin::~ChildPlugin: Child Plugin destroyed, Parent 
> plugin must not be destroyed yet!
> 
> Parent is setup before child, which is good. But parent also gets destroyed 
> before child which is of course bad. I can imagine tons of usecases where a 
> child needs to tell the base it is destroyed, i.e. base should _never ever_ be 
> destroyed before any of its children!
> 
> And to make things worse: I've just added a second child to my kte_linter 
> plugin in playground and that one gets loaded _before_ my base class. Since it 
> tries to tell the base class that it got loaded kwrite & kate segfault 
> everytime I start them.
> 
> So: Could someone look into the algorithm for setting up these plugins and 
> make sure the -depends stuff is taken into account? Or at least tell me where 
> this would take place and I could have a look.

kdelibs/utils/katepartpluginmanager.cpp looks like the right place for
KTextEditor plugins (i.e. stuff that loads in kwrite). kate plugins are
managed by something in kdesdk/kate.

Andreas

-- 
You are taking yourself far too seriously.
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


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