Everyone,
The MapView GPS issue has now been fixed as of daily build #947.
The MapView rendering issues have just been fixed today and the fix will be made available in a daily build later this week.
[import]uid: 32256 topic_id: 32067 reply_id: 130390[/import]
Kudos on wrapping up Android Mapviews Joshua, and kudos on the upcoming general release! These fixes should make my mapView busting android maps ship-worthy.
(And if you happen to slip in those pesky Android Push Notifications for the release, you won’t hear any complaints from me!)
Woohoo!! [import]uid: 79933 topic_id: 32067 reply_id: 130404[/import]
Kudos on wrapping up Android Mapviews Joshua, and kudos on the upcoming general release! These fixes should make my mapView busting android maps ship-worthy.
(And if you happen to slip in those pesky Android Push Notifications for the release, you won’t hear any complaints from me!)
Woohoo!! [import]uid: 79933 topic_id: 32067 reply_id: 130404[/import]
My mapview code is generating an interesting result in my Android devices.
This is a photo ( http://mapadomundo.org/android_debugging1.jpg ) I’ve taken of my ipad, iphone, galaxy ace plus and galaxy s3 and you’ll notice that in android there is a white rectangle separating the maps from the navigation menu.
The code that is generating this is:
myMap = native.newMapView(menuWidth,0,display.viewableContentWidth-menuWidth,display.viewableContentHeight)
Anyone know what can be causing this diference? [import]uid: 151732 topic_id: 32067 reply_id: 130513[/import]
guilovsh,
That’s the rendering issue that I said I fixed up above. It was fixed as of the newest daily build, today. Try giving that version a go. [import]uid: 32256 topic_id: 32067 reply_id: 130515[/import]
Joshua, this was built using today´s daily build… before that there was 2 rectangles 
It seems to be something to do with me trying to set a position to my mapview, it was supposed to be using x = 50 and seems to be using x = 100 for some arcane reason, hehe.
Thoughts? [import]uid: 151732 topic_id: 32067 reply_id: 130516[/import]
My mapview code is generating an interesting result in my Android devices.
This is a photo ( http://mapadomundo.org/android_debugging1.jpg ) I’ve taken of my ipad, iphone, galaxy ace plus and galaxy s3 and you’ll notice that in android there is a white rectangle separating the maps from the navigation menu.
The code that is generating this is:
myMap = native.newMapView(menuWidth,0,display.viewableContentWidth-menuWidth,display.viewableContentHeight)
Anyone know what can be causing this diference? [import]uid: 151732 topic_id: 32067 reply_id: 130513[/import]
guilovsh,
That’s the rendering issue that I said I fixed up above. It was fixed as of the newest daily build, today. Try giving that version a go. [import]uid: 32256 topic_id: 32067 reply_id: 130515[/import]
Joshua, this was built using today´s daily build… before that there was 2 rectangles
It seems to be something to do with me trying to set a position to my mapview, it was supposed to be using x = 50 and seems to be using x = 100 for some arcane reason, hehe.
Thoughts? [import]uid: 151732 topic_id: 32067 reply_id: 130516[/import]
guilovsh,
Yes, I know what issue you are talking about it. It’s a hardware acceleration bug in Google’s code. That’s the rendering issue that we’ve worked-around as of daily build #962 that I mentioned up above.
Which daily build were you using?
Can you also tell me what version of Android your device is running?
I need to know all 3 parts of the version number, such as 4.0.1 or 4.1.1.
[import]uid: 32256 topic_id: 32067 reply_id: 130720[/import]
guilovsh,
Yes, I know what issue you are talking about it. It’s a hardware acceleration bug in Google’s code. That’s the rendering issue that we’ve worked-around as of daily build #962 that I mentioned up above.
Which daily build were you using?
Can you also tell me what version of Android your device is running?
I need to know all 3 parts of the version number, such as 4.0.1 or 4.1.1.
[import]uid: 32256 topic_id: 32067 reply_id: 130720[/import]
I’ve used build 2012.962 to build the app running on those devices in my photo.
The galaxy ace plus is running android version 2.3.6 and the galaxy s3 is running android version 4.0.4.
[import]uid: 151732 topic_id: 32067 reply_id: 130779[/import]
I’ve used build 2012.962 to build the app running on those devices in my photo.
The galaxy ace plus is running android version 2.3.6 and the galaxy s3 is running android version 4.0.4.
[import]uid: 151732 topic_id: 32067 reply_id: 130779[/import]
Wait… this issue is happening on an Android 2.3.6 device? This sounds like a completely different issue then since that OS version does not support hardware accelerated native views. I think you’ve found an edge case that we haven’t tested… which means I might be able to find you a work-around for the time being.
Would you mind send us a small project that can reproduce this issue please? You can do so by clicking the “Report a Bug” link at the top of this web page. Thanks! [import]uid: 32256 topic_id: 32067 reply_id: 130835[/import]
Wait… this issue is happening on an Android 2.3.6 device? This sounds like a completely different issue then since that OS version does not support hardware accelerated native views. I think you’ve found an edge case that we haven’t tested… which means I might be able to find you a work-around for the time being.
Would you mind send us a small project that can reproduce this issue please? You can do so by clicking the “Report a Bug” link at the top of this web page. Thanks! [import]uid: 32256 topic_id: 32067 reply_id: 130835[/import]
Found out it was something to do with the positioning of the mapView having another display object on screen whilst on Android (it didn’t happen at all using iOS), but as this other display object wasn’t necessary, I just got rid of it and my app is now working as intended.
Thanks for your help, Joshua. [import]uid: 151732 topic_id: 32067 reply_id: 131867[/import]
Found out it was something to do with the positioning of the mapView having another display object on screen whilst on Android (it didn’t happen at all using iOS), but as this other display object wasn’t necessary, I just got rid of it and my app is now working as intended.
Thanks for your help, Joshua. [import]uid: 151732 topic_id: 32067 reply_id: 131867[/import]
