kconfig_compiler parameter forcing QString filename argument

[Marco Gulino]

I had the needing to handle a parameter-based KConfigXT class without having 
it singleton (i'm using instead a singleton container).  I noticed that the 
compiler was ready to have filename argument, but it just fallback to 
KSharedConfig::Ptr when not singleton.
In the attached patch i added a configuration parameter in the kcfgc file, 
ForceStringFilename, boolean. If true, it will add the filename argument as 
QString in the generated class.
Anyone has something against this? It shouldn't hurt currently existing code.

Thanks
	Marco
-- 
KMobileTools - Open Source meets Mobile Phones.
http://www.kmobiletools.org
RockMan's home page
http://rockman.altervista.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kconfig_string.diff
Type: text/x-diff
Size: 1633 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070513/2cc0032a/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070513/2cc0032a/attachment.sig>