You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new version with landmarks works great, but I'd like to give some feedback to try to make it even better:
The crosshair sometimes cannot be placed right on top of a landmark star, which may be confusing when having a cluster of landmarks around the same location. Of course, one can always zoom in in order to avoid any confusion. Just for the sake of comparison, in Google Maps the "granularity" of the movements when panning the map is smaller, so one can always hit the desired landmark by panning. On the other hand, in Nokia Maps the "crosshair" automatically drifts to select a landmark star when this is close enough to it.
If the database has many landmarks, their labels can obscure the vision of the map when zooming out. Perhaps it'd be a better idea to display landmark stars without labels, and reveal the label only for the landmark star right at the crosshair (the way it works in Google Maps and Nokia Maps).
When adding a landmark, "S60Maps" could be written in the "Category" section of the landmark in order to indicate that the landmark has been set using S60Maps (again, this is what Google Maps does when adding a landmark: "Google Maps" is written to the "Category" section).
Anyway, S60Maps keeps getting better and better. By the time the search option is implemented the program will really be a "killer" app, and another good reason to keep using our battered s60v3 phones. Well done Artem.
The text was updated successfully, but these errors were encountered:
The new version with landmarks works great, but I'd like to give some feedback to try to make it even better:
Anyway, S60Maps keeps getting better and better. By the time the search option is implemented the program will really be a "killer" app, and another good reason to keep using our battered s60v3 phones. Well done Artem.
The text was updated successfully, but these errors were encountered: