Johannes Sixt wrote:
 
> As long as the application can read and write its own configuration files in
> any location it likes, using KSimpleConfig or similar. For example, when kdbg
> debugs a program, it stores a configuration file in the directory of the
> program (to keep breakpoint locations etc).

KSimpleConfig takes either an absolute pathname or a relative name.

The relative name is converted to an absolute path by adding
"$HOME/.kde/share/config/". (Well, that's not how it is done, but that
is the result)

Cheers,
Waldo