Menu

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

#1
Quote from: Menion on July 19, 2024, 13:57:59@slarti76
OruxMaps ... funny comment @Tapio  ;D. Unfortunately, I believe there will still be more than slarti ;).

This is a general topic where all sorts of problems and features are discussed. Most of us use only a minority of what Locus Map can do, but -> when it's implemented and it does not work, it should be fixed (or removed for good), even if used only by a single person.

Back to problem > fix with the "map name" was only aesthetic. I'm also testing one Oruxmap and it works without a problem. Do you have this issue with all such maps?
Turns out this was a totally different problem, nothing with OruxMaps: I was still using the AFA build, and it affected all maps situated in folders other than Android/media or Android/data. Now that the Android/media way is working well, I switched to non-AFA and moved all my maps, and the problem doesn´t appear anymore.
As AFA is not an official thing, you can ignore this problem, I think.
#2
Quote from: michaelbechtold on July 16, 2024, 09:44:56I used sqlitedb for the most simple data collection for raster maps: lon, lat, ZL are the keys, pointing to a BLOB (the image).
This is a format many apps can handle, it is not a Locus invention.
Pardon me for not havin experience with that. All I'm saying is that it's no obvious without some experience/knowledge whether Orux is fundamentally different or not.
#3
Quote from: michaelbechtold on July 15, 2024, 20:42:01Hmmm, mbtiles and sqlitedb are quite common, beyond Locus, and not a Locus private bitmap format.
Well, OruxMaps is also "just" sqlitedb, so there must be more to it. What I mean to say is that the fact that Locus uses sqlitedb, doesn't mean the actual db structure is the same as in other sqlitedb maps. You can't judge from the outside.
#4
Quote from: Tapio on July 15, 2024, 15:32:27Out of curiosity - why do you use these kinds of maps instead of OAM/Lomaps?
As I wrote above, we have a friend who provides these. And OAM/LoMaps is really not the right comparison, as OruxMaps are bitmap, not vector. And when it's about external bitmap maps, I think there's no alternative to Orux, otherwise Locus only supports its own format, which I have never seen anywhere else. So Orux may be a competition, but offers a format that is at least somewhat known, whereas Locus-bitmap maps are not. I may be wrong there.
#5
Quote from: Tapio on July 15, 2024, 15:32:27
Quote from: slarti76 on July 15, 2024, 11:37:29I find it a little weird that two people thank you for a post basically telling me my bug report is of no importance? I don't complain when others report bugs that are of no concern for me...
Nah..., not about importance, just target audience. I apologise, my post was a bit unclear. I'm rather thinking this kind of stuff should better be handled via an official ticked because there's likely nobody to address in the user forum.
Fair enough, apology accepted. I decided to post it here, because Menion is in the audience ;), and the appearance of the bug exactly coincided with the fixing of that map name display bug, which also I was one of the reporters. So I think it makes sense to point that out here. Granted, correlation != causation, so maybe it's a coincidence the bug appeared at the same time.

And I'm using that Orux format a lot, as are some colleagues, because we have a friend who provides maps in that format. I had no reason to believe this is rare or common.
#6
Quote from: Tapio on July 15, 2024, 09:52:06Well, do you really think there's another person on earth using orux maps in Locus?
It's supported, and it worked before the initial display of map name was fixed (which it is), so am I not allowed to report that bug?

I find it a little weird that two people thank you for a post basically telling me my bug report is of no importance? I don't complain when others report bugs that are of no concern for me...
#7
Quote from: slarti76 on July 13, 2024, 22:22:11Ok, found out more: Only happens with offline maps in Orux maps format. Other offline vector or bitmap maps are restored correctly.
And more: Similar things happen when I choose an Orux map as overlay: It works, but when I switch map and then try to switch back using the "recently used maps" list, it's not shown. I have to select the map from the full map list again.

Should I make a video?
#8
Quote from: slarti76 on July 11, 2024, 09:04:47I noticed this a while ago, but now again after freshly installing Locus on a new device:
You may remember the problem me and some others were having that after start, the name of the current map is often not shown (instead "No map" or sth alike). This has been fixed, yeah - but for the worse: Now it's the opposite: The name is always shown correctly, but not the map. My devices, at least 2 tabs now, startup with empty map, but the last map name is correctly shown in the sidebar. I have to re-select the map to make it appear. Quite annoying, as you can imagine...

Nobody else having this effect?
Ok, found out more: Only happens with offline maps in Orux maps format. Other offline vector or bitmap maps are restored correctly.
#9
I noticed this a while ago, but now again after freshly installing Locus on a new device:
You may remember the problem me and some others were having that after start, the name of the current map is often not shown (instead "No map" or sth alike). This has been fixed, yeah - but for the worse: Now it's the opposite: The name is always shown correctly, but not the map. My devices, at least 2 tabs now, startup with empty map, but the last map name is correctly shown in the sidebar. I have to re-select the map to make it appear. Quite annoying, as you can imagine...

Nobody else having this effect?
#10
Quote from: Graf Geo on May 24, 2024, 11:30:18New function "Notification on invalid pause and pending recording states"
Where do I find that? I seem to be overlooking the right pointer. Searching in settings for "pause", "recording", or "notification" to no avail.

Which reminds me of something else:
Would it be possible to make the Locus version easier accessible? I first looked for this new function before I realized I didn't have the newest beta. Right now you need 3 clicks plus scrolling to get to the app info screen. At least the version could easily be shown in the bottom bar of the main menu (where it now says e.g. "LOCUS MAP GOLD"). And then perhaps make that bar clickable to get directly to App Info.
#11
Quote from: Tapio on May 11, 2024, 10:52:28This is a consistent friend now.
You cannot view this attachment.
I've been having that since the new side bar was implemented (1yr ago? 1.5?)- then Menion said he couldn't reproduce and I kinda learned to ignore it as aesthetic error and disappears once I select another map. But would be nice if it was fixed finally.
#12
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!
#13
HELP!

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.
#14
Quote from: Menion on March 27, 2024, 08:15:15@slarti76
missing change GPS start location > all was already suggested, so just one more note. "Navigate" should be still available in the Route planner main menu.

I'm thinking if your use-case should be used by more users, but starting navigation NOT from my current location does not make too much sense to me, sorry. Why you should do it? Prepare the route before you ride (with "Plan to") or once you are out to start navigation immediately (with "Navigate to").
Well, as I wrote, I do it at home where GPS can be insufficient. Especially in winter, I would start navigation before I go out into the cold, and of course I want to see where Locus is taking me, and possibly edit it. Which I also don't want to do once I'm out, with gloves on.
So it's not starting from another location then the current, it's specifically when you don't have a GPS fix and need to manually tell Locus where you're starting.
#15
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...