[Dev] Correct usage of mapplauncherd booster

asked 2018-11-27 22:54:38 +0200

Alex gravatar image

updated 2018-12-13 00:15:28 +0200

As there is no documentation I have the following questions:

  1. What is the correct way to use the native booster for accelerated app launching of a QML/C++ App?
  2. And are there any dependencies required?

Currently I am encountering the following issue in my application:

My .desktop file currently uses the X-Nemo-Application-Type=qtquick2 booster, but I want to switch to X-Nemo-Application-Type=silica-qt5 as recommended by the rpm-validator inside the SDK. The issue is that if I switch to the silica-qt5 booster I am getting a strange behaviour with the app cache folder:

Starting the app with the silica-qt5 booster from the desktop icon creates a wrong cache folder named mdeclarativecache_pre_initialized_qapplication-PID containing the actual cache folder. But the cache folder is correcly created if I start the app from the terminal.

Inside my application I am creating the cache folder the following way:

QString path = QStandardPaths::writableLocation(QStandardPaths::CacheLocation) + "/harbour-myApp";
QDir dir(path);
if (!dir.exists())
    dir.mkpath(".");

Has anyone an idea what causes this issue and how to resolve it?

edit retag flag offensive close delete

Comments

set correct QGuiApplication::organizationName and it's friends?

coderus ( 2018-11-30 10:38:18 +0200 )edit

@coderus Yes I am setting the following: setApplicationDisplayName, setApplicationName, setOrganizationName, setOrganizationDomain, setApplicationversion

Alex ( 2018-11-30 10:47:27 +0200 )edit

or i dont understand what is the problem exactly

coderus ( 2018-11-30 10:59:16 +0200 )edit

@coderus If I change the booster from qtquick2to silica-qt5 then the cache folder is created with the wrong name .cache/mdeclarativecache_pre_initialized_qapplication-PID/harbour-myApp instead of .cache/harbour-myApp

Alex ( 2018-11-30 11:31:17 +0200 )edit