Hello , can someone show how to read Application UID at runtime?
Symbian code snippet is ok
Thanks for help
Hello , can someone show how to read Application UID at runtime?
Symbian code snippet is ok
Thanks for help
Keep it simple, stupid (I think to myself)
borg - http://store.ovi.com/content/116105
The SecureID (usually the same as the UID3), VendorID and capabilities are process attributes, so just instantiate a RProcess object and read them from it.
The SecureID is also used to construct the private path of the application, so you could also read application directory's path and parse it to get the value (no Symbian API dependency in this case).
The UID3 should be also retrievable through CApaApplication (and derived classes) through AppDllUid, but somehow I don't see this working on Qt.
Last edited by ltomuta; 2011-01-31 at 21:49.
-- Lucian
I like this one!The SecureID is also used to construct the private path of the application, so you could also read application directory's path and parse it to get the value (no Symbian API dependency in this case).
Keep it simple, stupid (I think to myself)
borg - http://store.ovi.com/content/116105
This is appealing, you can just use QDir::currentPath() and parse it, it almost sounds cross-platform, but of course it isn't because such data-caging only exists on Symbian. It's not a great solution though because you might change the path somewhere in your app and then this breaks if you check afterwards. It's also easier to modify the app path externally to crack security.
If you're doing this for security purposes, use the RProcess method - it can't easily be faked without cracking the phone to turn off platform security. Also look in the RProcess docs for SecureId() to see a more flexible way of doing it via a security policy check.
http://library.forum.nokia.com/index...cessClass.html
Hi ,
i considered that it just sound as cross.platform but it is not ... anyway,in my case , that is not a problem ...i m developing for Symbian device using Qt4.6.3 , as soon as 4.7 will be released ,or Meego , or whatever i will reimplement what i have to.. btw i'm using it to avoid hardcoding UID as parameter to HomeScreen widget libray call , that , by its nature , is also platform dependent , furthermore , even deprecated on S^3 , if i understand it right. ..but it seems we are still on the way to Meego OS, and we will keep coding in Qt/Symbian for a while...
Thx for your advises and for the link ... i lack Symbian background so i appreciate very much when someone put the light on some aspect of the Symbian architecture ...
Keep it simple, stupid (I think to myself)
borg - http://store.ovi.com/content/116105
I'd be suprised if the strategy changes announced on 11th Feb don't still include Symbian & MeeGo in some way. MeeGo is too heavy a platform for the low-mid range devices with hardware cheaply available today.