2008/9/9 Julie S <[EMAIL PROTECTED]>: > >From my understanding, this is not necessary in every case of kapplication > >since QSettings can be accessed without the full QApplication file. > > ...
Hi Julie You may be right that the <QApplication> headers may not be required as often as <kapplication> was. While qApp->config() should be replaced with a direct call to QSettings, as you mentioned, still there are some qApp calls (formerly kapp), which still require <QApplication>, like qApp->palette() We may try later, when we got rid of most remaining errors, to remove QApplication includes, in order to see where they are really required. Sincerely Emanuel ------------------------------------------------------------------------- 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
