=== modified file 'plugins/Greeter/Unity/Launcher/launchermodelas.cpp'
+ case RoleAlerting:
+ return item->alerting();
Unrelated to this MP.
=== modified file 'plugins/Unity/Launcher/desktopfilehandler.cpp'
Off topic (since I see it being done elsewhere in the file)
+bool DesktopFileHandler::isTouchApp() const
+{
+ if (isValid()) {
+ QSettings settings(m_filename, QSettings::IniFormat);
+ settings.setIniCodec("UTF-8");
+ settings.beginGroup(QStringLiteral("Desktop Entry"));
+ return settings.value(QStringLiteral("X-Ubuntu-Touch")).toBool(); // false for empty or "false"
Rest looks ok to me, but would prefer launcher owner have a look.
Creating the QSettings object and parse the desktop file for each property read isn't very efficient. Any idea why we don't just parse it once at DesktopFileHandler creation?
=== modified file 'plugins/ Greeter/ Unity/Launcher/ launchermodelas .cpp'
+ case RoleAlerting:
+ return item->alerting();
Unrelated to this MP.
=== modified file 'plugins/ Unity/Launcher/ desktopfilehand ler.cpp'
Off topic (since I see it being done elsewhere in the file)
+bool DesktopFileHand ler::isTouchApp () const m_filename, QSettings: :IniFormat) ; setIniCodec( "UTF-8" ); beginGroup( QStringLiteral( "Desktop Entry")); value(QStringLi teral(" X-Ubuntu- Touch") ).toBool( ); // false for empty or "false"
+{
+ if (isValid()) {
+ QSettings settings(
+ settings.
+ settings.
+ return settings.
Rest looks ok to me, but would prefer launcher owner have a look.
Creating the QSettings object and parse the desktop file for each property read isn't very efficient. Any idea why we don't just parse it once at DesktopFileHandler creation?