Messages

[@tapio]

@tapio
from where were your new SRTM files? They are really so bad or it is some different format that is app unable to read correctly?

@CabrioTourer
I do not know. Are you able to simulate this with any other track? Steps to reproduce this issue are needed I'm worried.

@luce
damn, I'm looking at is since morning and this is quite a big problem.
... (later afternoon) ... uff, done, solved. Problem is in merging segments, but it should by highly improved now, thanks!

@balloni55
these are probably worst possible problems. This usually happens when in the app is increasing memory requirement more and more and in the moment, it runs out, app starts to be really slow. Without simulation on own device, it is close to impossible to do something with it.

May you please test it in the future and let me know if this happens again? If so, I'll try to run a simulation on my device and do some tests. Thanks!

Perfect! Thanks to your help & sample data, I think it is now even a little faster then on older Android 10- devices. So big thanks too.

[@T-mo]

@T-mo
- yes, the profile is used to compute times. Any big differences to reality?
- I'll think about it. This limit was created because GraphHopper service was paid and I had to reduce the amount of requests to be within certain limits. Anyway, I'll look at it ...
- graphical problem: how you did it? 

@Žajdlík Josef
Do you mean adding your own photos to our public LoPoints? This is currently a work in progress and will be available this year for sure. Otherwise please describe it a little more, thanks.

@balloni55
Thanks a lot balloni. I've just fixed the crash and updated the icon and generated a new version under the same ID, so just simply update to make it work again.

Hi guys, I've just uploaded a new Beta version 4.6.1.1 for the test. It has a united SVG rendering engine across the whole app so all MapsForge versions and also Locus Map itself now use same system.

If possible, give it a try and let me know if all is now correctly rendered. Thank you!

[@tapio]

@tapio
what you see is intent. I do this on more places in the app > next row is visible from the half to indicate, there is more content that may be scrolled.

@CabrioTourer
@freischneider, well, why not to ask here in more friendly and less official places right? . And answer is simple: the app is not limited by any device resolutions etc, so it should work. How much usable it will be? Hard to say. I was not creating any optimizations for foldable devices yet, so keep this in mind.

Hmm, who was it? 
I read it Tapio, but I thought that you want to keep it always down till you tap again. Never mind, my mistake. Implemented, will be in next app version.

I've today published a new version of the Locus Map 4 on Google Play. Today only for 25% of users, rest in next days. If anyone wants to test & play with it (or with the Locus Map Pro version), they are all already available on Google Drive!

Just for your info, why I do not communicate often as usual. Well, winter, some team planning, family require also some more time now, some illness and working on the system for one-time payments that consume most of my (not just) time. So nothing special and unusual, but just informing that app is still in progress   

Stay all healthy and don't be too much hidden at home like me, it does not worth it 

[@tapio]

@tapio
thanks for the info about the problem when switching between track & trackpoints. There really was an old problem so fixed now and even an improved time required to display a trackpoint, perfect!

@Pcmann
write to me a little more about your "It can be turned off in the "ZoomLevel" notification settings...". I do not perfectly understand, thanks.

@baegas
sorry, I've forget to test it. Seems to work fine for me.
What happens on your device? Click on the "select" button opens a system file browser. Here you choose a file from the DCIM directory? And then?

@luce
ah thanks. Another interesting issue that should be in the app for very long and I never noticed it. Interesting. Fixed.

@flyingman_ch
perfect, thanks, fixed.

Beta version 4.5.7.4 was just uploaded to Google Drive.

Finally, everything seems to be working as expected + a bunch of smaller fixes as usual. Please be aware, there may be unexpected malfunctions, that I should be able to immediately fix if known. Thanks.

I'll look at it, thanks.

Unfortunately, for more than a year I was not updating necessary build tools like Android Studio and many libraries around. But now it is necessary and I'm already more than a week stuck on it. Seems to be some technical problems in a few core-libs I use, so I communicate with other devs and try to solve it. Waste of time and no interesting updates = sorry. I'll publish and inform you about the new Beta as soon as possible.

Exactly this was changed in latest version @tapio, so all Androids now support this folder automatically.

[@balloni55]

@balloni55
your zip file contains some non-UTF8 characters and because of this, the app is unable to extract it (and crash). I've fixed it so the next version only notifies about the incorrect theme. Check the modified version from Willy, it works correctly.

Andrew, as visible on the screenshot here: https://forum.locusmap.eu/index.php?topic=7632.msg66285#msg66285 , there is a difference between selected and highlighted maps. It may be united, agree. But for now, the map with the colored background is the one, you see on the right side. Map with the name in highlight color (orange) is the one, currently active.

[@tapio]

@tapio
ah thanks. Problematic "line break" on the end of the first line. Fixed

@karlchick
the theme is unzipped to temporary cache if selected, to speed up work with it

@bezel
thanks, I've noticed this error in the automatically reported crashes. I have no idea why this happens but will look at it next few days.

@john_percy & @Andrew Heard
the new Beta version has just been generated. Please long click on the main menu button and enable "log to file" + logging of the "MAPS_CORE category. Try to simulate your issue and send me generated log from the "Locus/logs" directory, thanks!

@Andrew Heard sure I have, for example writing a blog post where I try to sum general info about theme support  . Hope you and others find there all answers. If not, I'll update it, of course, just ask, thanks.

Blog post on Medium.

And again, if something regards themes won't work as expected > share theme with me. John & Andrew, I'll prepare a version during next days ...