Locus 3.19.0: track point location modification possible glitch

Alf Onico shared this problem 1 year ago
Solved

Hello:

On Locus 3.19.0, once a track is recorded, if I want to modify the location of one of the points of the track, I do the following:

1) I click on the track

2) I select "edit on map"

3) I click on the edition panel wrench icon

4) I select "Insert/edit track point":: the selected point, the 2 branches of the track on each side, the 2 points on each side, and two additional intermediate points are highlighted in color (I can then drag any of these 5 colored points to a new location and accept the new location. This way I can interactively insert or move track points. But this is not very convenient if I want to move the point a long distance, for example if I want to move the first or last point of the track and then insert additional points to complete manually the recorded track).

5) I long press on the point of the track I am interested in. These give me two options, "Edit" or "Delete".

6) I select "Edit": the "SELECT LOCATION" menu (menu that was available on previous versions of Locus when selecting the "Edit location" option on a track point, option that was then differentiated from the "insert" option) appears.

7) I select "Select on map": this brings me back to the map, with the + and - zoom and "accept" blue icons.

8) I move the center of the map to the new desired location of the track point and I click on the "accept" blue icon, and then on the OK button at the top of the screen: the new location is not taken into account.

On previous versions of Locus, the steps 7 and 8 were achieving the desired modification of the track point location.

I also tried the option "projection" of the "SELECT LOCATION" menu: this worked as expected. I didn't try the other options.

Once it is understood that the option "Select on map" doesn't achieve the expected outcome, it is not a too serous problem as this option can be replace by dragging the point. But this is sometimes (very often in my case) not the most quick and efficient method, if the point has to be dragged a long distance.

Is this a desired limitation (in this case the option "Select on map" should be inactive ?), a glitch to be corrected in future versions, or did I misunderstood something ?

Thanks and regards

Comments (15)

photo
1

Update for Locus Pro version 3.20.0


Same problem.

photo
1

Good day,

I'm sorry for a late response.

Thank you for a very precise description of a problem. I was able to simulate a problem and successfully fix it. So issue will be fixed in next Locus Map version. Thank you.

photo
1

Hello

Just in case the problem was supposed to be fixed on version 3.20.1 (an not in a future version)

The problem is still there on Locus Pro version 3.20.1.

Additionally:

From the point 6 described in the initial post, the device slows down a lot (any map dragging takes a long time and at times for ever) and Android at times shows "Locus not responding", with no possible action on Locus other than shutting it down.

In case it helps:

I have an old version of Locus (3.5.3) on an old Android 2.3 phone.

The whole track point edition in this old version is (in my opinion) more intuitive (point edit and point insertion are two clearly separate tacks), and apparently significantly less ressource demanding (no slow down at all, everything going smoothly).

In my opinion and from the experience on the old and new version of Locus Pro, using for track editing the graphical interactive editing is perhaps not the best option for phones that don't have a fast processor.

Best regards.

photo
1

Hello Alf,

version 3.20.1 was published 1.11. , my fix was made 7.11. so it is not yet published.


Hmm version 3.5.3, it is so old, that I do not precisely remember how it worked. Anyway slowdown is surprising. This slowdown happen, no matter which and how long track are you editing?

photo
1

Hello


Many thanks for your reply.

The slowness and crashes happen on a track with approximately 1100 points.

I tried with a 4 point track: everything OK, reasonable reaction of Locus.

I suspect that my phone processor is too slow ?

Best regards

photo
1

Hello Alfonico,

so problem starts with increasing number of points ...


You wrote that this start since point six from initial post. In this point, you open dialog with "location options". So even this dialog appear slowly and all steps that follow, like pick a "map" button, move with map in dialog, etc. are slow?


I'll have to try, based on your description, to simulate this on older devices. And too slow ... in this, I believe this is more problem in Locus itself, because there do not happen any complicated calculations or tasks, that should slow down so much ...

photo
1

Hello

My bad. Sorry about that. 2 corrections to my previous messages.

1) The severe slow down starts not at point 6, but at point 4, as soon as I select "Insert Edit Track Point" and Locus zooms to the selected point of the track showing the point and the points on each side in green, and the 2 intermediate points between these 3 points in red.

I just tried it and Locus becomes practically frozen, any action (like dragging or double tapping to show the zoom buttons below the edit buttons) takes for ever..

Additional info that could help:

- A) If I am patient and manage to show the zoom buttons, and then I un-zoom a couple of zoom levels, the slowness decreases (that is, the reactions are slow but manageable). The problem then is that the 5 colored points are much to close on the screen for me to be able to do anything with them.If I zoom back two levels (back to the zoom level that is shown when clicking "Edit Insert Track Point", with the 5 colored points at a distance allowing manipulation of these points) the excessive slowness is back.

-B) Experiencing with zoom levels (no track edition going on, no track being displayed), I see that the slowness of Locus increases when the zoom level increases. It is not as bad as when trying to edit a track, but it is definitively there.

2) When previously I mentioned that the 4 point track edition worked fine, I didn't realize that my 4 point track had the points separated enough to have an edition zoom level smaller than the one needed to do a track edition on the 1100 point track. I experienced again with a 4 point track with close points requiring a large zoom level, and the slowness is there. The problem is therefore not related to the number of points but to the zoom level.

photo
1

Hello Alfonico,

thank you for a precise description of your problem. May you please write me what device and Android version you have?


Also, in top panel you may display zoom value and scale (same when you tap on bottom scale bar). When slowness begin, you have there scale set to 100% or Locus already rescale map to different value? Also are you using some overlays, map shading, WMS map? If so, may you check if this make a difference for you? Thank You!

photo
1

HelloThanks for your reply.

Device: Sony Ericson Xperia Active ST17i

Android 4.0.4.

No overlays, no map shading, no WMS, no vector map. Only offline maps in SQLite database format.

The following comments concern Locus with no track display or editing, therefore only concentrating on zoom issue.

Slowness increases progressively with zoom.

For exemple, with satellite imagery,

zoom 16, 100%, no sensible slowness

zoom 16, 200 %,, starting to feel some delays when dragging.

zoom 18, 100%, dragging delay becomes slightly annoying.

zoom 19, 100%,, dragging delay annoying.

zoom 19, 200%, dragging delay very annoying.

Have a nice week end.

photo
1

Hello Alfonico,

it is little bit complicated for me to help here. Best is if I'm able to simulate this problem on own device. So I'm trying quite big (0.5 GB) SQLite map on my old Xperia X8 which should be similar to your device. Maps are slower, but nothing so bad. But mainly! they are slow same in all zoom levels. Which is most weird for me ... there is no reason why one zoom level should be slower then different ( in case of 100% scale ).


Only idea, is to create a log when Locus is slow, by this method . In case, there will be any issue that print some information to log, it should be there.


Also last option ... too much points (mainly geocaches) / tracks visible on map?

photo
1

Hello

Many thanks for the time spent on this. Not a dramatic issue.

I am wondering if the problem is the resolution of the screen (small 3.5" screen) as the problem is affecting on this phone all the versions of locus, including 3.5.3 used on an other old and slow phone with Android 2.3 where no slowness is perceptible.

I will keep investigating from my end and post here if I find anything that make sense or if the proposed log shows something.

photo
1

Good morning,

you are welcome!

Smaller screen (lower resolution) should be faster then big, because Locus Map needs to load less data (map) to cover whole screen. Only what should dramatically affect speed of SQlite maps like you talk, is performance of database, or better performance of SD card. Maybe you should try some smaller map, or simply online map, if there will be difference.

photo
1

Hello


SDCard ! I'm an idiot not to have checked that!

I have revived an old very "temperamental" Sony Xperia Active ST17 that often has a mind of his own, that has Locus 3.19 and similar offline maps on his own SD Card.

All normal! (I should have tried that before!)

This rules out any problem related to Locus concerning the slowness at high zoom levels.

I am swapping the cards now. Will take a while to do partition copies to be sure that the problem is the card, or the phone itself, and not one of the other applications.

Many thanks again for the time spent on this slowness issue.

Regards

Alf

photo
1

Hello

Version 3.21.0: Problem solved!

Many thanks

photo
1

You are welcome, thanks for information!!