Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion on Map Drawing-Rendering #2941

Closed
JeanDom opened this issue Aug 13, 2016 · 4 comments
Closed

Suggestion on Map Drawing-Rendering #2941

JeanDom opened this issue Aug 13, 2016 · 4 comments

Comments

@JeanDom
Copy link

JeanDom commented Aug 13, 2016

For trip planning, users frequently study maps by zooming in-out, touch-scrolling to nearby towns etc., just to get acknowledged to an area they want to go to.

Currently, when displaying a new area, OSMand first draws details, as streets and roads etc., and this can take time, especially on slow devices. Names (as town or street names) are appearing only after that drawing process has finished.

SUGGESTION: SIMPLY GET NAMES BEING DISPLAYED FIRST.

With names appearing first (for example, Boulevard St. Michel) the user knows immediately whether or not he zoomed or touch-scrolled to the area he was looking for. If not, he can scroll further without waiting each time the whole drawing process finishes.

I don’t know whether this is doable, but it looks easy and would really improve the user experience of OSMand.

@vshcherb
Copy link
Member

This is already part of new rendering engine which is going to be released this year. To test http://download.osmand.net/latest-night-build/OsmAnd-qt-arm-nightly.apk

@scaidermern
Copy link
Contributor

This is already part of new rendering engine which is going to be released this year.

Sounds interesting. Is there any information about the new rendering engine? Does it finally use multithreading? Sorry for hijacking this bug report.

@JeanDom
Copy link
Author

JeanDom commented Aug 13, 2016

Thank you for the information.
I just tried the nightly apk with the provided link, but texts still appearing last (after everything else is rendered).

Thanks for your efforts

@vshcherb
Copy link
Member

It appears last initially, but then it stays on the movement and keep displayed. New engine will be multithreading. Also new engine works faster on newer devices and there are caching possibilities there. I will close that issue in favor of development of the new engine .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants