At first glance this seems a bit ugly, though I can live with it. I think we should have a bug about adding this flag to theme meta data eventually - which we'll need once third party themes can be installed and then we won't need this magic file anymore.
+ 706 qmlInfo(parent) << QStringLiteral("Theme '%1' has no '%2' style for version %3.%4, fall back to version %5.%6.")
Should/ could we have a specific warning about the theme being deprecated? So it's clear to an app developer that for instance they should stop using SuruGradient, and not just ponder why it's "incomplete".
why examples/1.3? seems a bit pointless if we won't have any old ones
- 191 return QUrl::fromLocal File(absoluteTh emeFolder) ; exists( absoluteThemeFo lder + "deprecated"); File(absoluteTh emeFolder) ;
+ 189 record.deprecated = QFile::
+ 190 record.path = QUrl::fromLocal
+ 191 break;
At first glance this seems a bit ugly, though I can live with it. I think we should have a bug about adding this flag to theme meta data eventually - which we'll need once third party themes can be installed and then we won't need this magic file anymore.
+ 706 qmlInfo(parent) << QStringLiteral( "Theme '%1' has no '%2' style for version %3.%4, fall back to version %5.%6.")
Should/ could we have a specific warning about the theme being deprecated? So it's clear to an app developer that for instance they should stop using SuruGradient, and not just ponder why it's "incomplete".