- I just received a notice from App World telling me that version 1.5.3 has been approved and will soon be available for download. This version includes native magnetometer support and it works quite nicely, if I do say so myself. Now that the logjam has been broken, I plan on submitting a series of updates in quick succession to fully exploit Point & View capability. More on this later...
Last edited by BuzzStarField; 05-31-12 at 11:33 PM.
05-31-12 11:06 PMLike 27 - This is great. i noticed that there is no more calibration for the magnemometer and was a bit worried at first, but its working excellently and doesnt seem to be affected by the magnet in the mini keyboard as well. Its just working as intended. Havent used this version extensively yet (obviously, lol), but if it holds up its awesome. In the release notes you mentioned how its the only change from the previous version and stuff, but its a great step forward. Keep working on it!06-01-12 12:02 AMLike 0
-
- 3This is great. i noticed that there is no more calibration for the magnemometer and was a bit worried at first, but its working excellently and doesnt seem to be affected by the magnet in the mini keyboard as well. Its just working as intended. Havent used this version extensively yet (obviously, lol), but if it holds up its awesome. In the release notes you mentioned how its the only change from the previous version and stuff, but its a great step forward. Keep working on it!
I have also discovered that the API gives the reliability level for for the sensor (a number between 0 and 3). My test app shows a reliability of 1 (rotten but not dead) when the PB is in the case. I am going to give the user a warning when the reading becomes unreliable The next release will be available on Thursday of next week.
As for the release notes, I was being a bit cheeky. The new API is "all" that you will notice but there are extensive changes in the underlying engine to handle all the new data the app is getting. I have been pushing AIR to the limits but if the dev is tricky (like I am) there are ways to make apps look pretty darn good. Being able to make our apps hybrids - part native - is a great thing. It's too bad that we had to wait so long for the ability to use ANEs.Last edited by BuzzStarField; 06-01-12 at 05:14 AM.
BlackStormRising likes this.06-01-12 04:59 AMLike 1 -
-
-
If you are using the mini keyboard case or you have been using the cradle-type charger with the magnetic connector, the compass will take a little while to re-calibrate itself.Last edited by BuzzStarField; 06-01-12 at 07:12 AM.
06-01-12 06:54 AMLike 0 - Headed for the dark skies of Vermont tonight so I can't wait! Thanks Buzz!!Sith_Apprentice and BuzzStarField like this.06-01-12 07:04 AMLike 2
- Please see my earlier post about calibration and magnetic interference. It's worth pointing out that RIM has done an excellent job of creating a self-correcting mechanism. It works quite well but I need a little time to learn about its quirks (and how to implement the re-calibration mode). Feedback from people like you is very helpful in addressing the problems and I appreciate your taking the time to post your report in the forum.
If you are using the mini keyboard case or you have been using the cradle-type charger with the magnetic connector, the compass will take a little while to re-calibrate itself.06-01-12 07:16 AMLike 0 - I can't replicate this problem on either of my test devices but this does not necessarily mean that nothing is wrong. Let's try to kick-start the auto-calibration mechanism by holding the device flat and turning it through 360 degrees, then hold it overhead and move it around a bit. Also it would be helpful if you had another compass app for comparison purposes - I use the one by mappau.06-01-12 07:35 AMLike 0
- Excellent, bought your app truly to support good dev's but I do find myself using it with the wife keep up the good workBuzzStarField likes this.06-01-12 07:49 AMLike 1
- To be honest, for me it wasnt showing the right direction while in the mini keyboard case. Then when I took it out, it took less than a minute (I think less than 30 seconds) to re-adjust itself. Before I knew it it was pointing North. Decided to put it back in the case and it was still working correctly after a couple minutes, pointing accurately in the right directions. Maybe the first time was just due to me opening the new version the first time with the new (awesome) api? selfcalibrated and then it was just working good.06-01-12 09:04 AMLike 0
- I want to thank you for all the feedback! It really helps me iron out the bugs. I still haven't figured out why one person has a "90 degree" problem but I noticed that the magnetic connector on the rapid charger will throw the reading out by 15 degrees or so.
This, coupled with another glitch adds up to an error of4535 degrees where I live - because I used the raw magnetometer reading instead of the one corrected for magnetic declination DOH! When I disconnect the charger, it takes some time to adjust itself so it gets a little frustrating.
I am going to submit a new release on Monday that fixes the declination problem and adds the reset button. It speeds up the auto--adjustment and should be useful despite the assurances in the API documentation that says otherwise.Last edited by BuzzStarField; 06-01-12 at 10:18 AM.
06-01-12 09:05 AMLike 3 - Sith_ApprenticeMod Team Emeritus
Just as a generally troubleshooting method, have you tried a hard reboot on the playbook to see if this corrects the issue?BuzzStarField likes this.06-01-12 09:09 AMLike 1 - So true! And I think that the dev is a smooth operator too
In the past, PB AIR apps were only able to do one task at a time, constrained as they were by AIR's notorious lack of threading. But now a BB10 dev can build apps that are internally multi-tasking in nature (if he knows how).
It took a bit of re-building, but P&V scrolling is now as smooth as manual scrolling always has been. The app is getting updates from the native side of the ANE (ActionScript Native Extension) at the same rate as the Adobe side updates the screen - 30 frames per second.
There are no bottle-necks in the code so I am going to be able to increase the frame rate even more (perhaps to 50-60 frames per second) by offloading some heavy-duty arithmetic to the native side and let the Adobe side concentrate on repainting the screen. I should be able to drastically increase the number of stars in the database too!Last edited by BuzzStarField; 06-01-12 at 01:04 PM.
06-01-12 12:43 PMLike 2 - If you are running 2.0.1 or above, you should have received a notification by now. If you are already running v1.5.2 you should be okay. Try going to My World and if necessary, tap the "refresh list" button. Let us know if you are successful.06-01-12 03:02 PMLike 0
- 06-01-12 03:21 PMLike 0
-
- I am having similar issues (got notification, but app stays at 1.5.2 in my world) and its bloody annoying.. Off to a very dark part of the UK and this baby will be fabulous with a glass of wine or two. trying the reset trick, will edit post if it shows 1.5.3.
PS Buzz: You seem to be mastering the dark arts better than a few weeks ago. Congrats on your hybrid native app
Edit: Mrs' playbook v2.0 OS just got update....All I can say is bloody h*ll! that's one he*l of an improvementLast edited by tinker2000; 06-01-12 at 03:49 PM.
BuzzStarField likes this.06-01-12 03:45 PMLike 1
- Forum
- BlackBerry PlayBook Forums
- PlayBook Apps & Games
What's up just got better...
LINK TO POST COPIED TO CLIPBOARD