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.

Show posts Menu

Messages - slarti76

Quote from: slarti76 on March 29, 2024, 00:31:47HELP!

I decided to move my main directory to Android/media - it first looked good, then I got the sad droid picture with "Whoops! dDS, code: 12521", and now I can't start Locus anymore. The same code appears all the time, after a toast "Restoring unfinished transfer of the main directory".

What can I do???

I updated to newest beta, just in case.
Ok, I solved the problem by connecting the phone to PC via USB and finishing the copying manually. After that it worked again flawlessly.
There were actually uncopied files, but no indication what kept Locus from copying them itself.

Anyway, I'm a computer expert who knows how to do this, but for others this would be a very bad outcome: No clear indication what happened, no remedy, Locus just broken. I assume re-install could help, as then Android would delete remaining files in Android/data, but, well, that would be data loss.

Menion, any idea what the error message means, internally? A more descriptive message would already go a long way, perhaps with the tip to manually copy with computer in case this repeatedly fails.

Anyway, no need to interrupt your Easter holiday for me ;)
Enjoy your (long) weekend, everyone!
The following users thanked this post: Andrew Heard
Quote from: freischneider on March 25, 2024, 17:33:48
Quote from: Graf Geo on March 25, 2024, 14:37:14You can still do this. Simply start the route planner directly instead of "Navigate to", then you can select the starting point on the map.
Use plan route by instead of navigating.
Thx. Not quite the same, because the "Navigate" button becomes the "Save" button and now one needs the detour through the menu. But better than adding and removing points.

Still, as written before, best would be to just have "Delete location" on the 3-dot-menu when "Waiting for GPS" is shown...
The following users thanked this post: freischneider
Locus Map / Re: [APP] - version 4.19.+ ( 9/2023 )
November 06, 2023, 11:07:12
Little weird observation in my recent holidays:
I split a track A into A1 and A2. Then both tracks had the same creation date/time (I think we discussed this a while ago, before that both parts got the current DT as new creation dates). Now when I sort the folder by "Created", it shows
  • A1
  • A2
- correct!

But when I reverse sorting, it still shows
  • A1
  • A2
- not really correct, as the second part of the original track is surely after the first part and thus should be shown before in the reversed list.
I assume, as both tracks have exactly the same created date/time, Locus then reverts to alphabetic sorting as "tie-breaker", which keeps A1 before A2.

As we agree that it's not helpful to set the Created DT of split tracks to the current DT, why not set the DT of the second part to its first trackpoint?
The following users thanked this post: Tapio, T-mo, Andrew Heard
Other features / Re: Online search
August 11, 2023, 09:56:37
I do see the complexity in combining all searches together, and I can live with having to select different search "means". But one major bother, that should be not too difficult to change is this:
Everytime the search scope is changed, there's a new, empty input field. Why not prefill with the search term already entered in another search? All the time I start typing into a search field before realizing I have the wrong search - then I change it and have to start from scratch (unless I thought of that and copy-pasted the term, which of course is also a bother).

PS: I just realized that this works between internal point and track search, but that's the only place I found.
The following users thanked this post: Jan Čapek, Andrew Heard
Locus Map / Re: [APP] - version 4.18.+ ( 8/2023 )
August 04, 2023, 07:50:50
Quote from: Andrew Heard on August 04, 2023, 01:17:34
Quote from: slarti76 on August 03, 2023, 13:18:55What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!
@slarti76 - thanks, hadn't used +codes before. Still slower (many more taps) than direct "share" of a point from my testing:
  • drag POI details down a few times
  • tap on "See all"
  • tap on +code (very little visual feedback BTW)
  • switch back to LM4
  • open Search (maybe side panel button)
  • paste clipboard (maybe more steps here)
Yeah, agreed, but
a) if we don't have another always-working solution,
b) surely no problem with parsing (well-defined as far as I understand)
c) at least last two steps could be improved if Locus adds a PlusCode support by automatically inserting clipboard content in search field (if it parses as PlusCode).
Heck, Locus could parse the clipboard when opening the search and automatically switch to PlusCode if it parses.

Honestly, I'm a little diappointed how the missing ability to correctly share positions from Google is waved away here. Menion et al should be aware that this is an ability that is absolutely crucial for "normal" users. OSM is nice and well, but let's face it, GMaps will always be more up-to-date. Rarely anyone relies on OSM POIs alone, so we all search stuff in GMaps all the time and want to easily enter the points in Locus. This is not something to just say "hasn't been working for a while, so what?"...
The following users thanked this post: michaelbechtold, Andrew Heard, freischneider
Locus Map / Re: [APP] - version 4.18.+ ( 8/2023 )
August 03, 2023, 13:18:55
Quote from: Menion on August 03, 2023, 08:11:37Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.
What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!
The following users thanked this post: michaelbechtold, Andrew Heard, freischneider
Hi there, also my 2 cents to the new side panel:
First, like it! Wouldn't mind some more configuration (e.g. rarely using LoPoints, so would rather be able to hide those lines).

What I'm not quite happy with yet is the theme selector: When you change the theme, you still first have to go through the options screen everytime, even though now there's a dedicated button for that. When switching between themes, I rarely also need to change the current selection, so this is a superfluous step.
Also, the "layers" button may be technically correct, but I think most users will be confused and would rather call this "theme settings", so I propose to use a cogwheel icon.
The following users thanked this post: balloni55, Tapio
Quote from: luce on March 13, 2023, 12:23:41I would like to add Management of Track Waypoints as No. 5.
Yes, please don't forget about this. There's a bunch of improvements needed here, many very basic (it's not even possible to multi-select and delete trackpoints!)
The following users thanked this post: freischneider, luce
Quote from: joeloc on March 11, 2023, 15:32:02
Quote from: Žajdlík Josef on March 10, 2023, 10:16:41You will also need to improve search. It should work simultaneously in addresses and points.
I completely agree. Locus search is pure usability horror from last century. A proper search is ONE SINGLE TEXT FIELD that simply searches EVERYTHING at once and shows results as they come in.

Making me decide in advance on where I want to search is just wrong on every level imaginable.
Even worse is when I start typing, realize I got the wrong "place" to search in, change it, and the input field is cleared - why's that? Makes no sense and would be easy to fix...
The following users thanked this post: lor74cas
Quote from: Menion on March 08, 2023, 13:38:21We have of course some plans and things that need to be done, but still ... simple question (that may influence my personal preferences). What is the biggest pain/requirement you mostly have with the app, I should solve during the next cca 3-9 months? I have in mind a few main categories:

1) management of the track waypoints (not surprisingly my favorite ;)
2) improve dashboard (missing items, simplify edit, improve charts, ...)
I would add
3) rotating labels in vector maps (or, rather, make labels non-rotating in relation to the (rotating) map. That's the main area where Locus just looks so much worse than other concurrent map apps - and of course it's not just looks when actually navigating...
4) better overlay handling, e.g. with overlay presets. For example, I have overlays with hike routes, skiing routes, public transportation stops, all are best at different alpha values, changing between them is such a pain that I usually don't use the feature, even though it's quite good in principle.
The following users thanked this post: Pcmann, michaelbechtold, Tapio
Locus Map / Re: [APP] - version 4.13.+ ( 12/2022 )
January 02, 2023, 18:40:44
Quote from: lor74cas on January 02, 2023, 16:39:13All locus notifications are active
Permissions for Locus are active except physical activity.
Out of my curiosity, what is "physical activity" in locus for?
Thank you
I think that's for the new (but beta) auto-pause detection.
The following users thanked this post: lor74cas, freischneider
Locus Map / Re: [APP] - version 4.13.+ ( 12/2022 )
December 22, 2022, 08:57:57
Quote from: Žajdlík Josef on December 22, 2022, 08:55:46Hi Menione. Backup files sent to the cloud are too big. The last one has over 0.5 GB. Most of the space is occupied by the track.db (800 MB) file. It is unnecessary to back up routes and points for the Gold version because they are stored in the Webplaner. Would it be too difficult to miss these files for Gold users from autonatic backups?
I strongly oppose leaving out the *.db by default. As an option, ok, but in my view, this is an absolute necessity - you can never rely on online storage service, I want to be able to restore my database even when e.g. Locus Web is down.
The following users thanked this post: michaelbechtold, Andrew Heard
Locus Map / Re: [APP] - version 4.13.+ ( 12/2022 )
December 09, 2022, 13:53:14
Quote from: Tapio on December 09, 2022, 06:48:48UI - I think SET/Recalculate position should be swapped. Typically, bottom right has OK (what you could say "Set" is, and it was there before). In my quick workflow I almost end up recalculating all when I just wanted to change routing profile.
My thought precisely. "Special operation" in the lower right is a recipe for disaster ;)
The following users thanked this post: Tapio, Andrew Heard
Locus Map / Re: [APP] - version 4.12.+ ( 09/2022 )
November 28, 2022, 16:40:37
Quote from: Menion on November 28, 2022, 10:34:58Yes, it should be by its "Created time" parameter. And well, you know. Waypoints in the app are painful and need a new system for handling them. Old problem ...
I could start again about my hope to at some point being able to create waypoints in the track editor, so they have a datetime. It's one of my biggest annoyances that waypoints created during recording have a timestamp, but when I forget them and want to add them later on, they won't have a timestamp that fits to the track.
Not all waypoints are POIs, like "hut", but things like "put on snowshoes", "removed crampons", etc. For those things, times are of relevance, especially if you use the same trail several times.
Well, I'll keep hoping... ;)
The following users thanked this post: Jethro10
Quote from: Menion on July 25, 2022, 13:15:46
There is more options on how to improve Presets. I'm still playing in my mind with two
- remember state before applying preset and allow restoring the previous state (already used in the navigation!)
- change the whole concept that you will be always in one active! preset (profile) and will just switch between them
I don't think the second option is a great idea: If implemented like that, every change of a setting *must* also change the active preset. That's definitely not what I want: If e.g. I change the map theme, I still want the original preset theme when I next activate it.
Only solution to this, I think would be that every change puts you in "unsaved preset", which you then can save, or discard when activating another preset. That would actually be cool, but I image it being rather complicated to implement.
Currently, I'm very happy with the existing system.
The following users thanked this post: Tapio, Andrew Heard, luce