Created attachment 59284 [details]
Version: unspecified (using KDE 4.6.2)
Package::filePath is no longer working in my python dataengine. It returns an empty QString for existing file.
Steps to Reproduce:
1. Download and install testcase engine.
2. Run plasmaengineexplorer in console.
3. Select name-melnichenko-nikita-make-progress-engine.
4. Get a Service with popup menu on data source '[jdbus] instance name'.
5. See output in the console.
>>> MakeProgressEngine: constructor
>>> MakeProgressEngine: init
>>> MakeProgressEngine: createSource([jdbus] version)
>>> MakeProgressEngine: createSource([jdbus] instance name)
>>> MakeProgressEngine: sources
>>> MakeProgressEngine: serviceForSource([jdbus] instance name)
>>> MakeProgressEngine: service is not created yet
>>> MakeProgress, ServiceInstanceName: constructor
>>> MakeProgress, ServiceInstanceName: registerOperationsScheme
>>> MakeProgressEngine: filePath("config", "InstanceName.xml") =
>>> MakeProgressEngine: path()+"contents/config/InstanceName.xml" = /home/nikita/.kde4/share/apps/plasma/dataengines/name-melnichenko-nikita-make-progress-engine/contents/config/InstanceName.xml
filePath("config", "InstanceName.xml") == path()+"contents/config/InstanceName.xml"
A walk-around for now could be: use Package::path() + "contents/path/to/your/file"
filePath definitely worked with KDE SC 4.4.
It occurs to me too.
4.6.2 on Chakra Linux
Can reproduce with example 'pyhello' in kdeexample repository
Is this still valid for KDE 4.8.3 or trunk?
Yes, this bug is still valid for 4.8.3. Check out my testcase, please!!!
This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.
Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting
If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging
Thanks for your understanding!