03-15-2011 10:26 PM
Also noticing that the header bar containing the settings will somtimes dissapear, hiding the clock, dev info button.
That's a sign that the qnx.systemtray process has died, completely. It used to happen, but was pretty rare. I've now had it occur far sooner than it ever did before, so it seems likely it's even flakier that it used to be. (I suppose it's a good thing that it's largely non-essential after you switch to development mode.)
(I've confirmed that the task has died with "pidin" via SSH. There's no way to restart it other than be rebooting the sim.)
03-16-2011 02:07 PM
Has anyone else had trouble getting into developer mode?
03-16-2011 02:21 PM
John, had similar troubles.
Try clicking on the Back button. It may be necessary to have the state saved.
Also note you can usually do a bottom-swipe to close the settings pages. It wouldn't work in an app, of course, but works fine for the OS screens.
03-16-2011 02:26 PM
03-17-2011 03:36 PM
The second question I have is about permissions. I noticed that 0.9.4 uses permissions and my app uses the shared object so I need to use them. I put <permission>access_shared</permission> into the blackberry-tablet.xml.
I'm not prepared to assume that the documentation in the Developers Guide is correct on this item.
It says that to "Access the shared file system" you have to use access_shared, then goes on to list the three APIs supposedly involved:
The thing is, there's no good reason to call it the "shared" filesystem, as far as I'm concerned, unless they really meant to refer to the areas under the shared/ folder, which is space shared by all apps.
The SharedObject info, however, is generally used for app-local data, where the file goes into a subfolder of the app "sandbox", and no other apps can see it.
I have a feeling whoever wrote that may not have fully understood what access_shared was really for, or may simply have had a hard time explaining it clearly. Possibly the word "shared" could simply be removed and it would just say "Access the file system"... if that's correct, then it is required with SharedObject and everything else, but it seem unlikely to me since there should be no need for special permission just to write to the app's sandbox. (And no need for one with the word "shared" in the name.)
03-17-2011 03:45 PM
I hate this generic threads - there is no way to mark anything resolved and you don't know who is answering who.
I think you are right, access_shared required to access shared folder only. SharedObject is not actually stored in there (I don't even think it is stored on disk). Want to send bug to docs?
The fact that it is not promting user is temporary, in the final version it will - and it will return some sort of permission denied when you try to access shared without asking this capability
03-17-2011 03:57 PM
So should I take out the permission access_shared and resubmit since I am only using the local shared object? I have already submitted my signed app with access_shared in there so will that cause a problem?
03-17-2011 04:37 PM
sky858: you don't have to. It will just prompt user for this. And if user say yes or not it does not really matter because you not actually using it. However if you want a clean version I would remove it - but wait until maybe actuall playbook release so you can test it properly.