I always prefer my maps to point North, on my phone. (North being top, when phone held in portrait orientation)
Ok, my in all my apps I always rotate the map to look in the direction I am moving. Preferences 
The extension has been updated to version 1.2, see the first post
1 Like
Version 1.3
Errors have been corrected regarding hiding the map button and the information displayed on elements when clicked.
Great, thanks for adding the rotate map feature. 
Some minor bugs that I ran into:
Using the navigation features of MIT works on the simulator/companion but when compiled it doesn't. It throws an error.
Also when the rotate map feature is on and you add another marker, the marker is off-set.
Thanks, great .aix
I just compiled the project's AIA and everything works perfectly. Please tell me which blocks in your project are causing the problem.
Here is the issue. The problem is triggering when I request the line of path between 2 points. In the simulator it works, no error. After compiling into an app the problem above shows. This is done when the line based on a json list is applied.
I created a line with just two dots and it works fine in both the companion and the compiled app. Check if your JSON list is well-formed.
Yes checked that and the Json point format seems ok, in fact on the simulator it works perfectly hence the line (made of multiple points) shows on the map but its after compilation that the error occurs.
When I create a circle and place it under the location sensors, it moves not only the circle but also the map along with it. Ideally, it would be better if only the circle moved according to its changing position.
And also this is very important:
This blok doesn't work.
The extension has been updated to version 1.4, see the first post
2 Likes
¡Excelente!
I know, I asked for a lot (and I was even a little embarrassed), but these were really necessary things. I haven't examined it closely yet, but it looks nice.
Muchos Gracias!
1 Like
Great extension
Some minor things:
When the MapClick is triggered and the map is rotated the location is not accurate.
Here some issues, that I faced with Request Navigation - OnCalculating;
OnCalcuting takes a very long time to give results. With the longer routes it freezes (ANR).
Even though I haven't moved from my spot, kmRemaining decreased on its own.
timeRemaining is also gives wrong results.
I don't know if speedRoute is working correctly or incorrectly, as I said, I haven't left the computer :).
- it should be also a option to turnon/off the Voice.
On request calculations it seems working, I get the point of the route (onCalculating) but then it centers it self on the middle of the route even tough asking to move to a different point.
Also with the rotate feature when you press on the map it locates the wrong latitute and longitude.
Other then that this .aix is imporving everytime there is an update...but not there yet
The oncalculating process doesn't take long, just a few seconds. What does take time is the location sensor giving you your location, especially if you're inside your house. The kmremaining and timeremaining calculations also depend on the location sensor; if you're inside your house, it can give incorrect locations and produce inaccurate results for these parameters. Try it outdoors and you'll see it works fine. I've tested it with routes of up to 1000 points and it's never crashed on me.
Regarding whether or not to remove the voiceover, I've noted that for future versions. I've also created a test extension to switch from OSRM to Stadia Walhalla as the route server, which is also free but much more efficient, since OSRM is primarily designed for car routes and sometimes takes you on paths meant for cars when walking. When it's working correctly, I'll include the Stadia server in the maps extension
I'm currently working on getting the extension to detect when you're off route so it can automatically recalculate it..
1 Like
Okay, I'll try it outside too. Yes, OSMR is nice, but it offers very limited usability. I've never heard of Stadia Walhall before.
However, the biggest problem I'm experiencing with the extension is when creating a new line or circle. Every time, the map first changes zoom and then moves to that point. When I want to shorten the driveline as I progress along the road, a lot of clutter occurs. I suggest you take this into consideration as well.
I don't quite understand how you're doing it. Whether it's rotating or not shouldn't affect the coordinate calculation, because these are based on the map. If you double-click on an element, it will give you the current coordinates. And if an element has a drag option, when you move it, it also gives you the coordinates. The centering effect is that when you double-click on any tile, including Google Maps, the map zooms and centers it. Keep in mind that if you're in finger rotation mode, the zoom effect is eliminated, and vice versa. Generally, when you create an element, the extension centers it on the map with the given coordinates.