Hello Everyone,
I'm concerned about this last update:
> Log Message:
> -----------
> include kapplication.h ==> QApplication
>From my understanding, this is not necessary in every case of kapplication
>since QSettings can be accessed without the full QApplication file.
I don't have the documentation handy at the moment, but it was clearly noted in
the QT C++ Programming guide that since QSettings values were
available--because they are initialized during the contructor of
QSettings--including the full Qapplications was unnecessary.
So, this may get things to run, but we better scrub the files later, when we
want to minimize the overhead.
Maybe a better way is to remove the include kapplication and compare the error
log with one with it included first to determine which ones really need it. If
kapplications is just there to get to KConfig hopefully we could tell easily.
I think mot KConfig ==> QSettings at this point. I don't know about function
call parameters yet.
Well, those are my thoughts.
Sincerely,
Julie S.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
