I'm trying to port existing wp7 app to wp8 and there is problem with maps. Map is made from 6 tiles. Everything is working well, but pinching is terrible. Works much worse than on WP7.
Anything changed in WP8? What I have found is small information from microsoft presentation which says that in WP8 some things from pinch and strech were improved
Extends the ManipulationDeltaEventArgs class
PinchManipulation property
Provides center point for the original and current gesture
my 0.02$: On WP8 you should move from Bing Maps to using the new Nokia Maps control # http://www.developer.nokia.com/Resources/Library/Lumia/guide-to-the-maps.html
If you have just ported your app to WP8 from WP7 then everything should work as before. The only problem might be if you have hardcoded some display resolution values in your app, for computing the pinch gestures for example, and the app in now running on device with 720p display - it has height 853px instead of 800px.
Anyway as Justin noted you can switch to new Nokia maps in WP8, but you can still use Bing maps as well, although they are deprecated on WP8. You just have to reference new WP8 Bing maps library in folder:
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Libraries
Related
I have a RN app that uses react-native-maps. I was able to successfully render the Map in the Android and iOS Emulators, but when I build it out (using Expo), the app works but the Map renders as a Gray screen with the Google logo on the bottom left-hand corner.
I have an API key and have enabled all of the essential APIs in the
Google Developer Console.
I have only tested this on a physical Android device.
So,
What am I missing?
Should I consider using Mapbox instead?
EDIT:
I did not add anything to a build.gradle or anything of the sort from the Android Studio end; just front-end stuff. Is this required?
I face same problem of greyed map, when use LocationView of react-native-location-view. Greyed Map resolved by Enable Maps SDK for Android. Follow as shown in
Enable Maps SDK for Android in your developer console
https://console.developers.google.com
I've created a simple WebVR app using A-Frame. On my phone it will launch into VR mode however it doesn't seem to be well configured for my model of google cardboard. The two images are two far apart and I just get a double vision rather than 3d effect.
I can get a good VR experience on the google cardboard app by configuring cardboard to the specific model of google cardboard. Is there an equivalent that can be done in google chrome to tell it the model of cardboard I'm using / display distance etc?
Take a look at this issue thread on GitHub:
https://github.com/aframevr/aframe/issues/2117
The solution toward the bottom from garrethwilliams explains what you can do to tweak A-Frame to work with your model of the phone until the webvr-pollyfill is updated with specs from the newer Android devices.
I used Nokia here map (version 2.5.4) within my web application, but if I open my web site on mobile device (Tested on Android 4.x Nexus 7 ,IOS7 IPhone5c ) it is unable pinch-to-zoom.
I also found a similar issue:
Nokia Here JavaScript API disables pinch zoom in iOS
I also try downgrade here map API version to 2.2.3, pinch-to-zoom is working but I cannot use the built-in marker function in 2.2.3 version.
Any solution/suggest?
I found the solution!
First we detect client , if client device is mobile/tablet
Than load 2.2.1 here map , otherwise load newly version
In my case , i also need use custom icon marker with overlay text .
In newly version , i can use https://github.com/heremaps/examples/tree/master/maps_api_for_javascript/demos/text-on-icon-marker to meet the requirement.
Unfortunately , in 2.2.1 above solution is not working, but we can referring to http://api.maps.nokia.com/en/playground/examples/maps/map_objects/customsvgmarker.html using SVG image instead of bitmap .
But this solution only working on Android 4.x .
IOS is not working
Please use the newest Here Maps API for JavaScript 3.0, you can find more information on developer.here.com, this Version is optimized for mobile usage.
An extensive set of examples for the API can be found on the API Explorer.
There is also a migration guide available to help your upgrade from 2.x to 3.x
I'm building a cross-platform HTML5 app which needs to contain a map. Google Maps and Nokia Here Maps work well on all other platforms, but Windows Phone's browser behaves oddly. The map can be moved around, but I need another finger on the screen for the panning to work with another one.
Can anyone give me a proper solution what maps should I use or how do I make Google Maps or Nokia Here Maps work? The only feature I need from the maps is that I need to put pins on it that open an overlay box when clicked.
I try google maps in default web brouser on my Sony Ericsson Active (android 2.3.4), but I found that multitouch zooming doesn't work.
Is google maps api v3 support multitouch zooming or anybody know scripts for this.
UPDATE
I found next information: http://www.html5rocks.com/en/mobile/touch.html:
On the Android Gingerbread Browser (tested on Nexus One and Nexus S),
there is no multi-touch support. This is a known issue
(http://code.google.com/p/android/issues/detail?id=11909)
And this feature implemented in android 4.0 (http://code.google.com/p/android/issues/detail?id=11909#c19).
Yes, the google maps api v3 supports multitouch. It's possible to see it on a iOS with the Safari. I think the browser is the problem on android devices. It does not send the touch events to the map, because it interprets the touch commands as webpage zoom. So it seems to be currently not possible to use multitouch with google map on androids default browser.