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 - menion

Pages: [1] 2 3 ... 714
1
Hmm, that may be a problem ... we will see at the start of May. Then I'll try to do something with it ... (push Arcao a little or start coding by myself ...)

2
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 23, 2019, 13:02:29 »
@john_percy
1. hmm point screen is really old and is on top of my priorities right after I get rid of map & LM4 stuff. In the moment you do a tiny change in "new point screen", the back button is equal to "save". The correct system is made in "Track edit screen" and the same needs to be applied here.

2. look on this from the opposite side: on the trip, you are in an interesting place you want to save. And the fact you play with map does not change anything on the fact, that you stand on the place you want to save.

There are situations where the first or second option is useful. Currently, Locus Map use GPS if available. If you do not like this behavior, feel free to change it in the settings > points & tracks > new point default location.

Bringing a paper map to the digital world is not always ideal I think. Here (digital world) we have one powerful information you miss on paper map: your location.

@poutnikl
do you know any other application that sort data by the center of the map? At least Google Maps definitely do not do this. Locus is a little special here.

---

Anyway in config.cfg exists parameter "gui_data_point_list_sort_by_gps" that should affect this. Expect fact it is incorrectly named, it also does not work as expected in all cases, heh.

So in the next version will be in "expert settings" new "Sort data by" settings for this. As I see, we had to discuss this long time ago. My bad > default parameter is already set to "map center", sorry :). So I'll leave it as is.

---

So based on the above paragraph, an important change to keep system same (no matter what I think now): sorting of content in the app will remain by default by "map center". Searching, to keep consistent, will use the same settings, so by default, it will use "map center" as searching center-point. Global agree?

@Andrew Heard
hmm, if possible: give a try next Beta version that will come this week. If there will still be this problem, should be again possible to share with me your current track database + current map coordinates you have? Thanks

@slarti76
hmm I see where this "toast" appears, but to fix it correctly, I need to know steps to simulate it. It should appear only when you try to do something and by some accident, no trackpoint is selected (so it should work only as a rare warning in case of a problem).

3
1. as I know, users of Free version report and generally help with developing a lot less than Pro version users ... which is expected

2. exactly for these users, nothing changes! Locus Map Free will be Locus Map and will be the main active app with same (and growing) functionality. So maybe there is some missunderstanding about how we will change the current Free/Pro model?

4
Ah thanks Christian for the remainder of this topic.
The same issue as Andrew have on the video, happens to me as well a few times. I'm checking code, but all seems to be correct. Maybe refresh of the map happens too early, so I added them half second delay. Hopefully, it will help.

Not sure what exactly is the problem with Route planner. Anyway, here I remember that I saw some problem with Android system, that incorrectly detected restoring of the main map screen, that caused some remaings of the plan even on the main map screen. I wasn't able to find out why this happens. Will be watching it ...

5
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 22, 2019, 09:45:32 »
Hmm "nearest" in sorting of tracks should really be nearest. Even a "map center" used in case of disabled GPS is little weird (most probably should be "last known GPS location").

For your use-case, best should be to use "search" function where is really easy to change from GPS to "map center" (just two clicks).

Hmm area of Karlovy Vary, do not know this are well, but definitely city & castle Loket . There should be also very nice path between Loket and Karlovy Vary along that Ohře river (hike & bike).

6
Discussion/New features / Re: Update of map core (2019)
« on: April 22, 2019, 07:16:24 »
@michaelbechtold
isn't scaling same in current Pro version? It should also somewhere around 70% jump to the previous zoom level. To prevent this, it is needed use "zoom lock" function.

Agree with the world map: I've added the condition that the map has to have at least zoom level 11 to appear in quick map switch.

There still appears vector maps optimized for "world map", which is hard to detect. Maybe just by its name "world"? Hmm.

@john_percy
understand. How to solve this ... maybe some option "snap to zoom levels". I'll look at it.

7
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 22, 2019, 06:45:58 »
@Andrew Heard
hmm firstly because in the search screen is in "Track around" visible "My location", it means you have GPS enabled, at least Locus thinks it. Otherwise "Map center" should be in this field.

In sort by nearest, the same system is used. So if GPS is enabled, the last known location is used, otherwise, map center is used.

To be true, I see no reason why it should give incorrect results, just check this GPS on/off state, thanks.

@Christian
if possible, wait on next Beta or new version. This is a solvable problem, so no worry.

@slarti76
funny comparison to Word :). Oki agree, messages removed.

"To edit the track, tap it" message also inform that there is no activity running. I do not see a problem with this message to be true.

8
Discussion/New features / Re: Update of map core (2019)
« on: April 21, 2019, 20:31:53 »
Hi Michael,
not sure I perfectly understand what is the problem with scaling.
Are you playing with vector maps? Then manually set scale should be preserved when scaling by hardware buttons.

Anyway, app currently computes real resolution (pixels per meter) for every map zoom and during zooming, it searches for optimal zoom level from the source map, where scale will be as low as possible.

Quick map switch: hmm world map should be there only in case, there are no better alternatives for some smaller local maps. Is this your case? Btw. defined "map center" has no effect here. Only coverage and it's relation to current map center is important.

9
Discussion/New features / Re: Update of map core (2019)
« on: April 21, 2019, 17:02:48 »
Uff, done.
So added clever delete function that should really delete only content, not anymore needed by any other installed theme.
As a bonus, I created a function that validates, that really all necessary resources are available.

Test on your side (after a backup of themes) is of course welcome. If anyone will be interested in improving this "validate" function, let me know. Currently, it only checks resources defined as "file:/" in xml file.

@john_percy
because Locus Map does not use full system offered by MapsForge library, but still try to render map tiles and draw them in own system, I'm worried, this does not have a simple solution.

100% scaling ... hmm, there is no longer anything like "100%" scale as before. Anyway in top toolbar may be still visible, the scale of the current map. So by fingers, app snaps little to this 100 %. Then you may zoom by buttons by predefined step that should be same as one zoom in vector maps.

10
Themes - Vector maps / Re: [Theme] TOTM
« on: April 21, 2019, 14:26:49 »
Ah sorry for the miss-understanding.
I pointed "refuse" on myself. It is me, who refuse to do this in the first row. Definitely not any problem on the side of MapsForge developers.

11
Themes - Vector maps / Re: [Theme] TOTM
« on: April 20, 2019, 22:58:04 »
Hello Magellan,
refuse is probably the correct word :). Improved rendering system was created in time, it wasn't sure if MapsForge developers will continue in work or not. In these times, there is a new version of their library and it is not compatible with the old V3 system that Locus use for LoMaps and custom themes like this.

Adding support for all these custom parameters also to new V4 system is little "overkill". We currently have the same problem: we will need to completely convert internal themes into this new system and from what I know, it will be quite complicated task because many special features that I made years before is not supported in new MapsForge library ... just for your info.

12
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 20, 2019, 22:04:30 »
Thousands? This happens for all of your tracks? I tough we solved one similar issue in the latest version, so this should happen only for newly modified tracks!

With my work on many places last weeks, I have little mess in head what and where is already fixed. Anyway, I'll definitely publish regular Beta version next week, so if with this beta problem still appear, I'll add into the app method to fix this problem for the whole database.

13
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 20, 2019, 17:57:08 »
Hello Tapio,
this issue happens when you move a track between folders and probably also when you do some advanced edits. In the next version, this should be fixed. Sorry for this.

14
Discussion/New features / Re: Update of map core (2019)
« on: April 20, 2019, 08:32:39 »
Hmm, I was thinking some time ago about the option to delete selected theme directly from UI. Anyway, it may be a problem in case of shared images by more themes.

It is doable I believe, it will just take some time (will have to analyze all themes in define and create list of safe icons to delete). So if there will be a bigger interest, I may invest half a day and do this ...

15
Discussion/New features / Re: Update of map core (2019)
« on: April 20, 2019, 00:14:39 »
Perfect :).
It is now finally possible to have two or more XML files in the same subdirectory and all these files appear for selection. It is then easy to share the same icons for themes without messing the root "_themes" directory as was necessary till now.

Pages: [1] 2 3 ... 714