David Faure wrote:
> 
> On Thursday 23 November 2000 20:24, Richard Moore wrote:
> > Frerich Raabe wrote:
> > >
> > > Hello,
> > >
> > > I'd like to add a second constructor to KAboutApplication, which allows
> > > to specify a custom KAboutData object - this is especially useful for
> > > libraries, which have no way to pass a KAboutData object to KGlobal.
> > > Are there any objections, suggestions or recommendations on this?
> > > Otherwise I'll just go on and add that second constructor.
> 
> How can a library be a KUniqueApplication ? I don't understand.
> 
> > Go for it - we can use this for applets, extensions, styles,
> > Konq viewers...
> 
> ?? How can extensions, styles and parts be kuniqueapplications ?

I assumed we were talking about 'about...' dialogs. Perhaps I was 
wrong. I would like libs such as styles etc. to be able to specify
a KAboutData and get the usal KAboutDlg stuff.

Rich.

> 
> KApplication doesn't have such a constructor [anymore], I don't understand why
> KUniqueApplication should have it, since it's supposed to be a drop-in
> replacement for the former.
> It's KCmdLineArgs that gets the about-data.... A KApp/KUniqueApp constructor
> that takes the about-data directly is an open door to apps without cmdline
> args support...
> I guess applets are a case of unique-apps for which cmdline support doesn't
> matter, though. But not necessarily unique either.
> 
> --
> David FAURE, david@mandrakesoft.com, faure@kde.org
> http://www.mandrakesoft.com/~david/, http://www.konqueror.org/
> KDE, Making The Future of Computing Available Today
> See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

-- 
     Richard Moore		rich@ipso-facto.freeserve.co.uk
http://www.macromedia.com/	rjmoore@macromedia.com
http://developer.kde.org/	rich@kde.org