I am writing a kio salve. The slave works in general, is loaded and all is fine, except one strange thing:

All kDebug() messages are only generated when I check "unnamed app" in kdebugdialog. This although the slave has a correct name and actually this name is preceding all the kDebug() messages generated.

- I _think_ the .protocol-file is correct and read, since the slave (protocol) is offered.
- I do provide kAboutData and store it in KComponentData in kdemain().
- I tried adding the slave manually to ~/.kde4/share/config/kdebugrc and it is shown and can be checked, however this is not connected to the installed slave. The generation of kDebug() messages still is controlled as "unnamed app".

So my conclusion is that I somehow miss one thing in the correct registration of the slave. However I cannot find any hint in several examples I checked. And, needless to say, the documentation of how to write, install and register a new kio slave is, well, little, apart from the auto generated documentation of the kde api classes.

Any hints for me ?!? Thanks !
arkascha

Ok, found the solution myself.
So here for the records:

I called kDebug() for the first time _before_ setting the kComponentData.
That call registered the slave in the debug environment. A registration
a) under the name 'unnamed app', since no name had been set until now and
b) wont be changed setting the kComponentData afterwards (which makes sense)

Cheers !