Re: make kdeui loadable by styles, kill/merge kdefx
Matthew Woehlke <mw_triad <at> users.sourceforge.net>
2007-07-03 01:33:39 GMT
David Faure wrote:
> On Saturday 30 June 2007, Matthew Woehlke wrote:
>> David Faure wrote:
>>> On Friday 29 June 2007, Matthew Woehlke wrote:
>>>> I know I've heard people talk about wanting to kill/merge kdefx, and I
>>>> recently learned that the reason it exists as a separate library is (at
>>>> least in part) due to some issues loading kdeui outside of a KApplication.
>>> ... and problems when unloading libraries.
>>> (not depending on kapp is something we have already fixed in kdelibs4).
>> $ designer -style Plastik
>> Fatal error: you need to have a KComponentData object before
>> you do anything that requires it! Examples of this are config
>> objects, standard directories or translations.
>> What's going on here I think is the code tried to do KGlobal::config(),
>> KConfigGroup() and readEntry(), and it choked at one of those steps. I
>> don't think it's doing anything else as far as using objects in kdeui.
> Well, none of that has anything to do with KApplication itself.
> The application class isn't the problem.
> However if you get this error, it means you (well, not you, but
> the plastik style) should instanciate a KComponentData instance.
Ah, yes. Well, that's not as easy as it sounds, but after some
KComponentData ctor hacking, thanks to Matthias Kretz, it seems to be
working. So it looks like you're right that kdeui is usable... as long