On Mon, 29 Nov 1999, David Faure wrote:
> > -----Original Message-----
> > From: Waldo Bastian [mailto:bastian@suse.de]
> > Sent: Monday, November 29, 1999 10:38 AM
> > To: kde-cvs@master.kde.org
> > Cc: kde-core-devel@kde.org
> > Subject: Re: kdebase/kdesktop
> > 
> > 
> > On Sat, 27 Nov 1999, CVS by dfaure wrote:
> > > kdebase/kdesktop init.cc,1.2,1.3 main.cc,1.38,1.39
> > > Author: dfaure
> > > CVSROOT: /home/kde
> > > Sat Nov 27 19:57:07 MET 1999
> > > Update of /home/kde/kdebase/kdesktop
> > > In directory zeus:/tmp/cvs-serv13663
> > > 
> > > Modified Files:
> > > 	init.cc main.cc 
> > > Log Message:
> > > Added call to KUniqueApp::start, remove support for nofork 
> > (done in KUniqueApp),
> > > and removed the fork() (done in KUniqueApp).
> > > IMHO KUniqueApp should remove the --nofork from the args, just like 
> > > QApplication and KApplication do, AFAIK.
> > 
> > Yes. The problem is that the arguments are not always passed via
> > QApplication/KApplication so that they won't remove arguments neither.
> > 
> I'm not sure I understand that.
> Isn't the way it works usually : when *Application, at any level, processes
> an arg, it removes it from the list ?

Yes. That is how it should be indeed.

But when you launch a second KUniqueApplication, the constructor is
avoided, if possible. And the arguments are passed via DCOP to
newInstance() without ever seeing a KApplication or QApplication
constructor. This is not what you want/expect. (And since last week,
even the first launch, sends the arguments via DCOP to newInstance()).

So what we need is a "filter arguments from this QCtring-List"-function
for both QApplication as well as KApplication.

It's a bit overkill IMHO to use the Q/KApplication constructors just for
that, although it would be the easiest way.

Cheers,
Waldo