On Sonntag, 31. August 2003 00:08, Matt Zimmerman wrote:
> On Fri, Aug 29, 2003 at 10:34:39PM -0700, Mike Markley wrote:
> > A quick summary of this bug:
> > Arson, a KDE CD burning application, includes two .desktop files to
> > associate certain files with it:
> > /usr/share/mimelnk/application/x-iso.desktop
> > /usr/share/mimelnk/application/x-cue.desktop
>
> And presumably another application also wants to include these files? Is
> KDE's file association system really so broken that two programs cannot
> both declare themselves able to handle a certain type of file?
You can do that, one program after another in the order the user wants to
prefer a certain program for a certain mimetype as a handler. The issue here
is that not every program written for KDE is provided by the KDE project so
the packager has to take care of integrating files like the mimelnk's that
the programmer maybe mistakenly added for his own make; make install laziness
into the desktop by packaging.
Ralf
>
> --
> - mdz
--
We're not a company, we just produce better code at less costs.
----
Ralf Nolden
[EMAIL PROTECTED]
The K Desktop Environment The KDevelop Project
http://www.kde.org http://www.kdevelop.org
pgpXsm4sOS68C.pgp
Description: signature
