Re: [trinity-devel] $KDEHOME

I don't read c++ very well. Seems to me that if $KDEHOME is not explicitly defined then Trinity defaults to $HOME/.kde3. Yet the comments in kstandardirs.h declare $HOME/.kde as the default. ============================================= kdelibs/kdecore/kstandardirs.cpp: ============================================= if (!localKdeDir.isEmpty()) { if (localKdeDir[localKdeDir.length()-1] != QChar('/')) localKdeDir += QChar('/'); } else { localKdeDir = TQDir::homeDirPath() + "/.kde3/"; } ============================================= ============================================= kdelibs/kdecore/kstandardirs.h: ============================================= * @li KDEHOME: The directory where changes are saved to. This directory is * used to search for resources first. If KDEHOME is not * specified it defaults to "$HOME/.kde" ============================================= 1. Should the comment be updated or the code in kstandardirs.cpp? 2. With all the branding issues that have arised, is $HOME/.kde3 a good choice? Or should the default be changed to $HOME/.trinity? 3. Trinity is supposed to be compatible with KDE4. In KDE4 the default for $KDEHOME is $HOME/.kde. Seems then that if $KDEHOME is explicitly declared in a KDE4 environment that Trinity will trash a user's KDE4 settings. Seems the best way to avoid any mess is to use a default $KDEHOME setting like $HOME/.trinity or $HOME/.kde3. I prefer the former as that avoids potential conflicts with older KDE3 systems too. I think this issue needs attention. Darrell --- On Mon, 3/14/11, Darrell Anderson <humanreadable(a)yahoo.com> wrote: