Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - john_percy

Pages: [1] 2 3 ... 35
Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: December 07, 2018, 18:17:03 »
@menion Of course, it hasn't crashed since the first three times! Could you point me to the instructions for sending a bug report, please.

Sent from my moto g(6) plus using Tapatalk

Versions / Re: [APP] - version 3.35.+ ( 7. 12. 2018 )
« on: December 07, 2018, 10:39:10 »
1. New version "stops" (crashes) unaccountably from time to time. Possibly linked with moving map centre(?) :(
2. Cannot access the different styles of custom themes in new version. Tried a phone restart but no difference. I've checked bug on both Tobias's Elevate/Elements and my Voluntary themes -- there seems no way to access the Styles menu. Connected to changelog item: "fix: incorrect icons of popup menu selector of custom themes" (?) >:(
Edit: Styles pop up menu still works on Mapsforge v4 maps.

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: December 03, 2018, 10:21:40 »
you know that app has some more serious problems with labels because of the older part of MapsForge V3 library.
I am aware of the problem with labels and Mapsforge v3 library. But this is a Mapsforge v4 multilingual map -- doesn't that use v4 library?
The usual problem is labels not extending outside the boundaries of the tiles -- this is almost the reverse: the label is only displayed outside the relevant tile.
In any case, the issue is not simply to do with rendering as the map displays correctly on switching to it from a standard map but incorrectly on changing zoom. The standard maps don't display this effect.

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: December 01, 2018, 20:48:07 »
Using a Mapsforge Multilingual map of Great Britain from OpenAndroMaps and any theme (eg internal General theme or my Voluntary ML theme) I'm finding that zooming from ZL15 to ZL14 results in portions of the text layer not being drawn (left). The text layer is drawn if I change to a standard LoMap and back to the ML map (right).
Example: Long Buckby N52.29568 W001.09262:

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 26, 2018, 14:15:57 »
Attempting to do a search using Geonames or GNS on new beta. Start typing into search box, auto complete options offered from past searches. Tap on one of these (eg "pooley bridge"), text appears as "ListItemParams(id=0)". Delete this nonsense character by character,  Locus crashes when last character has been erased. (Sorry, can't upload screenshot in current mobile configuration.)
This search behaves correctly in current Pro version.

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 21, 2018, 11:08:25 »
Btw. is it really useful at all? Two taps to close app instead of "swipe up" and home button.
On my old MotoG i needed full screen to get enough screen space. "Swipe up" was frustratingly imprecise and could easily result in scrolling the map several kilometres and losing my place insteada of opening the soft buttons. So, yes, the Exit button was very useful.
It isn't needed on my new Moto G6 as use the fingerprint detector as a back button instead.

Troubles & Questions / Re: Backup manager, Restore is not complete
« on: November 20, 2018, 12:16:56 »
I too found I had to shut down the phone and restart it for the restore to be effective. The automatic restart of Locus is not sufficient.

Sent from my XT1039 using Tapatalk

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 20, 2018, 00:01:36 »
The "Exit" option near the end of the main menu has disappeared from the latest beta. Is that intentional?

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 14, 2018, 20:39:21 »
Thanks. I'd tried that but then realised these maps were in a different folder than the one I had been looking at. Now sorted!

Sent from my XT1039 using Tapatalk

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 14, 2018, 20:31:22 »
I removed a world map and now get this error at start up. What to do?

Sent from my XT1039 using Tapatalk

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 05, 2018, 13:00:38 »
1. OK. I'd forgotten I'd edited config.sys.
2. So, does it only learn from recorded tracks, not simply following navigation? That seems not so good.
3. 1000 years is an awful long time!!!  ::)

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 05, 2018, 11:49:38 »
So, I think
1. Remove Google navigation if it doesn't work ;)
2. Thanks for the explanation. Does that mean the algorithm hasn't changed, just my usage or driving? (I guess I noticed the difference when I changed back to Pro version after the beta expired.) I presume it does know the difference between my walking habits and my driving habits? I would welcome an improvement in any case. An estimate of 8 hours for a 1 hour journey seemed a bit extreme.
3. I don't know whether the distances are preselected or if they are randomly produced at intervals during the navigation. My first preference if the distances are preselected would be to select from "three quarters of a mile, half a mile, a quarter of a mile, xxx yards". Otherwise, "xxx yards" below 999 yards and probably (but less certainly) "xxxx yards" between 1000 yards and a mile.

Versions / Re: [APP] - version 3.33/3.34 ( 26. 9. 2018 )
« on: November 04, 2018, 11:58:34 »
1. Navigate using Google gives an "over query limit". Not sure how long this has been the case.
2. Navigate using Brouter gives a ridiculous estimated journey time for car journeys. This is new, though the time used to be up to twice as long as real life.
3. Voice commands in Brouter car navigation give "in nought point seven miles..." etc which sounds very odd to an English ear. Better would be "in one thousand yards" or "in three quarters of a mile". This is long standing.

Some of the original data had "holes" in it but I thought that had all been tidied up.

SRTM Void Filled elevation data are the result of additional processing to address areas of missing data or voids in the SRTM Non-Void Filled collection. The voids occur in areas where the initial processing did not meet quality specifications. Since SRTM data are one of the most widely used elevation data sources, the NGA filled the voids using interpolation algorithms in conjunction with other sources of elevation data. The resolution for SRTM Void Filled data is 1 arc-second for the United States and 3 arc-seconds for global coverage.

Versions / Re: [APP] - version 3.33.+ ( 26. 9. 2018 )
« on: October 24, 2018, 10:21:19 »
I agree. "Problem we can't identify" is hard for inexperienced user to resolve.
"Please log in again" might be more helpful.
Possible cause is that I had recently changed my Google password.

Sent from my XT1039 using Tapatalk

Pages: [1] 2 3 ... 35