"new KRun" is only meant to run absolute file paths and so breaks when we get a
service with relative entryPath() like when finding a KCModule.
The tempFile argument causes this call to be asynchronous as to not block the UI
"new KRun" is only meant to run absolute file paths and so breaks when we get a
service with relative entryPath() like when finding a KCModule.
The tempFile argument causes this call to be asynchronous as to not block the UI
The tempFile hack has David Faure's blessing as new KRun is only meant for when opening files and the like. KRun::runService normally blocks but doesn't when we do the tempFiles thing. This fixes opening eg KCMs (search for eg "Splash" and add it to favorites).
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
Yes, but please add a comment about porting to KRun::runApplication once https://phabricator.kde.org/D1902 is merged in and you can rely on KF 5.24 :-)