This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
manual:faq:locus_performance [2016/03/15 12:51] – created mstupka | manual:faq:locus_performance [2017/02/07 12:03] – mstupka | ||
---|---|---|---|
Line 3: | Line 3: | ||
---- | ---- | ||
There are a few factors that can slow the app response down which may be sometimes annoying. To prevent Locus lagging try to adhere to the following principles: | There are a few factors that can slow the app response down which may be sometimes annoying. To prevent Locus lagging try to adhere to the following principles: | ||
- | ===== Extra map layers ===== | + | ===== Turn off extra map layers ===== |
Map features like [[manual: | Map features like [[manual: | ||
- | ===== Too many displayed | + | |
- | Each device has its limits in displaying databases. | + | **[[manual: |
+ | ===== Do not visualize too many points and tracks ===== | ||
+ | If you visualize | ||
+ | |||
+ | **Geocaches** contain large amount of information, | ||
+ | |||
+ | **Geocache waypoints** engage your device system even more than their original caches - we recommend to display as many waypoints as you really need for your immediate work. | ||
+ | ===== Do not display too many or too large map items ===== | ||
+ | Some KML/KMZ maps or other files that are stored in the " | ||
+ | ===== Vector maps are rendered within the app ===== | ||
+ | Vector maps like e.g. our [[manual: | ||
+ | |||
+ | <WRAP center round important> | ||
+ | In case you maintain all the principles above and yet, the app is lagging, try to follow [[manual: | ||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | Is this article useful for you? Please rate it: | ||
+ | {(rater> |