On Tue, Oct 23, 2001 at 09:53:24AM -0700, Carl R. Witty wrote: > "Ivan E. Moore II" <[EMAIL PROTECTED]> writes: > > > On Tue, Oct 23, 2001 at 03:42:06PM +0200, Josip Rodin wrote: > > > On Mon, Oct 22, 2001 at 12:13:31PM -0700, Chris Waters wrote: > > > > > information. KDE ends up seeing 2 different sets of information for > > > > > the > > > > > same binary and can (and usually does) gets confused. > > > > > > > > Can you be more specific about this "gets confused" part? > > > > > > I think he meant "KDE user ends up seeing... and gets confused". > > > > no. I mean KDE ends up seeing 2 different sets of information and gets > > confused. > > > > ie. > > > > KDE provided .dekstop file is used to tell KDE information such as > > mimetypes, > > help file locations, etc.. The Debian provided (or rather generated) > > .desktop > > file does not and thus KDE see's one that has this info and one that does > > not > > and does strange things which is usually that it prefers the later .desktop > > file it reads..which could very easily be the Debian generated one. > > What does KDE use to decide that two .desktop files are "the same"? > Is this visible to the user? Could we just make sure that the > .desktop files created by the menu system are distinct from those > that come with KDE?
the name of the .desktop file is irrelavant..however the executable name is really where it keys off of ..so in order to make the Debian entries distinct we would need to change the binary name...however this would still not take care of what we need..we need to not duplicate things... Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
