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

#706
@flyingman_ch
thanks very much for reported bugs. The problem with a missing number of items in folders will be fixed in the next version (this week).

Unfortunately, I'm unable to simulate this "If I have logged a cache, Locus will exit when I click the Back button." problem. Does it happen with every cache you log? Immediately after you confirm the log?

@Andrew Heard
you will see in the next version if the change I made today helps. Anyway, you may agree that it looks really weird when you completely "covered" info panel with buttons :). Fortunately for you, in LM4 this won't happen :).
The following users thanked this post: Andrew Heard
#707
@Andrew Heard
in the next version, the drag area will be a lot bigger, so give it a try, thanks.

@slarti76
not sure how often you switch landscape/portrait, but you may quite easily cover this by the system of Presets.
The following users thanked this post: Andrew Heard
#708
Thanks balloni. It works for you correctly?
The great advantage is that in case you use the app mainly in the landscape, you may have full top bar with buttons, no matter, how long is it, if you use a tablet or tiny old small phone, etc.
The following users thanked this post: Andrew Heard
#709
After a quite long time, a new Beta version on Google Play.

Among a few fixes & updates, there is mainly a nice new service called "Web service library". Probably some of you know this older list of WMS maps we collect here. Half of them already do not work etc ...

New Beta version offers a new service that collects these web services (option "Add to library" in the context menu of any added map) and mainly offer them to users. On the background, the server test these maps every day to validate it still works correctly. We have a few things in the head to improve, but for now, some feedback will be welcome.
The following users thanked this post: Tapio
#710
No worry, I do not plan to remove it ... just my head needs some time to validate that it is a good perspective method on how to do it. But yes, most probably I'll add few more parameters over time and tell Michal to wrote some blog post about it :).
The following users thanked this post: freischneider
#711
@Žajdlík Josef
hmm so it seems to be bug on Android 5.0 so thanks, this start logo removed from this Android version.

@zossebart
forget mentioned tool is intent in this case. I'm a) still not sure if this is a really useful method and b) I believe it needs few more parameters, not just related to navigation but at least for track recording.

@lor74cas
heh ... it's quite extreme in your case. Garmin & Geoching4Locus are not inside in Locus Map, so there is no chance. Rest ... it is complicated. Every "big service" needs own notification that say user that it's running and consume device resources. Since Android 7 or 8 (not sure now) you may specificy in the app system settings, which notifications will be visible (as on attached screenshot) so you may remove them over this tool.

@slarti76
I can't imagine it display sooner. G5 is not so old so 10 seconds is way too much. The same delay is in all other app starts or just for the first time? Weird, anyway really can't imagine why this happens and how to speed up. In the first moment, Locus notice that UI is visible, it displays loading dialog.
The following users thanked this post: lor74cas
#712
Ah, that's the point. Thanks Tapio, attached files helped. Will be fixed in the next version.
The following users thanked this post: Tapio
#713
@tapio
- thanks for the tip. If we decide to all hiding of all panels, display of settings, in this case, may be useful.

- top bar > I may guarantee that it won't be possible to add actions there, like before. The top panel will remain as a static panel with information. But the final design was not yet done. Notch areas are a problem that needs to be solved, agree.

@Andrew Heard
The default value for orientation source is "Auto-change", not GPS.
I mentioned two-finger rotate as a complication to display the current status. Because if you rotate manually, once you stop, the map does not rotate by compass but is still rotated.

Sensor compatibility mode > interesting. This mode uses the older technique to compute device orientation. It is slower and you may notice that map rotation is not so fluent, it is shaking a little. Not a big problem and because on some devices, non-compatible mode gave incorrect results, we left in the app this fallback option.

Scroll of bottom main menu > good point. Not sure how to solve it, but I'll try. Definitely not an intent.
The following users thanked this post: Tapio
#714
Permanently hidden bottom & right panel: sorry guys, but not. Both panels are made for quick access to features. The simple logic is: if the panel contains something, display it, if not, hide it. Hide it permanently? Only in rare cases like @luxcalor wrote for example. Anyway, these rare cases may be solved by Presets, so use them. On the second side, accidental hiding of panels causes us only trouble (on the support web) and may confuse users.

I'm also not sure about automatic hiding of empty bottom panel ... have to think about it more. Because as @tapio correctly wrote ... empty panel (automatically hidden) won't appear by double click ... and confused user may only ask "why?".

"Small buttons in the bottom" > got it, thanks John. It is indeed incorrectly wrote shrinking of buttons in case of insufficient space.

@Andrew Heard
it's correct. Map rotation works when GPS is on and the map is centered. I plan to improve the style of these two buttons, so will keep this issue in my mind, thanks. There is also a fact, that you may rotate map by two fingers, which little complicate life :).

GPS > major part of source code is shared between both versions (and will be), so all these technicals, like functions that take care about GPS, are identical.

Problem with "Show view": may you please just check settings > GPS & sensors > Orientation > Compatibility mode. If you change this, "Show view" still displays 180° difference? I just can't find any reason why this should not work on the south hemisphere :/.

The following users thanked this post: Andrew Heard
#715
Hi,
third alpha version. Base changes are described in the news after the app start.

I've added a new option to insert "Toggle settings" directly into the function panel. Every item has to be exactly specified and prepared in the code, so now it's only about missing "Magnifier" and "Scale lock".

I'm also sure that it will be similar like with presets ... everyone needs a different option in the function panel, otherwise, the app is useless :). Fine, I got it. So please, don't ask me to add this and this setting, I won't do it (at least not now). I made this to test usage of such option and also try to solve two missing functions that does not have its space in default easy-to-use layout. Thanks for understanding.

Known problems to solve (not yet always sure how or "if")

  • Unreliable drag & drop in the main menu
  • Configurable position of zoom buttons?

Download here.
The following users thanked this post: luxcalor
#716
Troubles & Questions / Re: Wms issue
December 29, 2019, 13:39:32
Hello

"can't add" isn't enough information to find our the reason.

Sent from my Pixel 2 using Tapatalk

The following users thanked this post: c2h5oh
#717
Hi,
so second alpha version with various UI/UX improvements that should solve most of the problems we discuss here. The main difference you may notice is hidden top panel & zoom buttons. It may be re-enabled over map-screen content settings.

Please just keep in mind, that what I try to achieve here with your help, is basic universal settings suitable for most of the users. Because you use the app for so long, you have specific needs, that I'm sure we will solve soon or later as well ;).

Known problems to solve (not yet always sure how or "if")

  • Too much icons in bottom panel (functions below centering button)
  • Missing "Scale lock" feature
  • Configurable number of items in main menu
  • Configurable position of zoom buttons

Download here.
The following users thanked this post: tramp20
#718
Oki, understand. No more comments related to this button needed. I'll create a working updated version to the next app version.

Theme? Please specify, not sure I understand.
The following users thanked this post: erfi
#719
The created poll was made to help me decided about need for some components & color themes. There is still not yet done base look. Currently, I have on the table six version we discuss about.

And about possible configuration: you know me. I usually do features in the two steps. First, base, not too configurable and later, after some discussions and feedback, I'm adding options (when it makes sense).

It will be similar here. Hey, we have enough time to tune it to satisfy at least 95% of use-cases, so no worry :).

Btw: I'm not doing re-design because I want to do re-desing. I'm doing this to remove some limitations of old design and remove some problems we suffer for ages (based on support & own experience > like too much buttons at start for new users, fixed bottom panel, important buttons too far from fingers, etc.) I'm registering all your comments and will really try to find usable solution.
The following users thanked this post: michaelbechtold, Andrew Heard, freischneider
#720
Hi guys,

based on testing, your comments, own thoughts, there is progress.

But I will still appreciate some help. So short (5-10 minutes) poll for those of you, interest in future of Locus Map: https://forms.gle/ro1xvZoRjwqTnXCP9 . If know similar, not active users, please share it.

I believe that 100+ votes will be enough to give me nice overview of the preferences of current users, thanks!

@tapio
Not sure how exactly will it look like, but an option for hiding of the zoom buttons will be there. As well as search in settings (I have most of the work done regards this task).

"Created time" in point detail: why this may be useful? I understand this in the case of trackpoints (to know time between two trackpoints), but in the case of waypoints?

Menu > more: will be fixed in next Beta, thanks.
The following users thanked this post: Žajdlík Josef