Q: kconfig without kaboutdata behavior

2014-04-03 Thread Harald Sitter
ahoy, I just wanted to ask whether it is still mandatory to have a KAboutData instance set to have classes such as KConfigShared work in a convenient fashion (e.g. KConfigShared::openConfig() will open the applications config as long as qapp::applicationName is set). In my particular case the

Re: Q: kconfig without kaboutdata behavior

2014-04-03 Thread Alex Merry
On 03/04/14 09:34, Harald Sitter wrote: ahoy, I just wanted to ask whether it is still mandatory to have a KAboutData instance set to have classes such as KConfigShared work in a convenient fashion (e.g. KConfigShared::openConfig() will open the applications config as long as

Re: Q: kconfig without kaboutdata behavior

2014-04-03 Thread Harald Sitter
On Thu, Apr 3, 2014 at 12:30 PM, Alex Merry alex.me...@kde.org wrote: On 03/04/14 09:34, Harald Sitter wrote: ahoy, I just wanted to ask whether it is still mandatory to have a KAboutData instance set to have classes such as KConfigShared work in a convenient fashion (e.g.