Messages

[thanks]

How is it possible, you so quickly noticed new Beta version? 

And thanks for the report. Version fixed and re-uploaded. I was completely changing background system how the app comunicate with the Locus Store (for upcomming changes) and minor issue was undetected.

@Menion @voldapet
Doesn't Locus support the improved text break algorithm in Mapsforge? In the screenshot, the town name ought to break at a hyphen.

(As in https://github.com/mapsforge/mapsforge/pull/1392 )

In the startpost you write: LM4 required but here with classic 3.68.2 it works great too.

Ah... is LM3 able to use Mapsforge V4+ maps? Do you use OAM maps?

Sorry, Dont't know. I only use the latest OAM maps (V5).

Both LM3 and LM4 can use the latest OAM maps. Obviously you get a better result with a theme designed for OAM.
Both LM3 and LM4 can display the latest Lomaps, using the same renderer and themes as for OAM maps, though once again you get best results with a theme designed for Lomaps or for both OAM maps and Lomaps.
Both LM3 and LM4 can display older Lomaps with Locus's own renderer. Themes have to be designed for older Lomaps or they won't show on the theme selector.

Inzwischen habe ich mich mal genauer mit den Presets befasst und ja, hier scheinen diese tatsächlich hilfreich zu sein. Die Möglichkeiten waren mir in der umfassenden Form bisher nicht bekannt.

Habe eins für OAM angelegt mit dem passend eingestellten Elevate Theme und ein zweites für LoMaps mit dem gewünschten internen Theme. Damit ist der schnelle Kartenwechsel inkl. Thenenwechsel möglich. Mal sehen, ob sich das so im Alltag bewährt.

Danke für eure Anregung diesbzgl.!

Gibt es denn auch ein automatisches Beenden, Holger??

Maybe an interesting improvement for Locus user and developers: "DTM Czechia v2" has been released which is based completely on precise LiDAR data.

Hi Mips,
ich kann nicht für Christian sprechen, aber ich kann berichten, dass Christian aus dem Urlaub zurück ist und an einem Preprocessing arbeitet, das die Verwüstungen (*) in Nordics kompensieren soll. Erste Erfolge hat er bereits.
Haben wir also noch ein wenig Geduld.
Gruß
Michael

(*) die sind akademisch nicht einmal falsch, aber für die Nutzung der OSM-Daten ein Problem.

Hallo dann doch noch mal... 

da ich in der Zwischenzeit doch noch ein paar motivierende Rückmeldungen erhalten habe, bin ich wieder aktiv geworden und starte die Stage 2 der Entwicklung. Der Preis nähert sich damit der 100 Euro Marke, was aber noch zu optimieren ist. Es gilt aber auch noch die Präzision unter Beweis zu stellen, denn es kommt ein anderer Chip zum Einsatz.
Für mich spannend, denn es ist auch ein komplett anderes System.
Wer es nicht braucht, den kann ich verstehen.
Wen es interessiert, da würde ich mich über eine Rückmeldung freuen.

Nebenbei gesagt: Meine aktuelle Version läuft mega gut und liefert top Positions- und auch echt super Höhenwerte. Wenn auch noch für die allgemeine Anwendung zu teuer, ich freue mich über das Ergebnis, was ich mir erhofft hatte.

Also dann,.... wer Lust hat bleibt dabei.

Liebe Grüße,

Olaf

The secondary function, by the long click, is the temporary hide of all points/tracks.

@Menion the new long tap doesn't provide any visual feedback. You don't know whether anything has changed or the long tap has done anything until you return to the map. Could the long tap also return directly to the map?

[new Beta 4.17.2.2 version]

Hi guys,
(most probably) final solution published in the new Beta 4.17.2.2 version. I got your point, but do not fully agree with all.

Main use-case, the clearest to basic users: unload points. So this will be the primary function of this button. After confirmation, the button is disabled and counter reset so I believe, it is clear what this function did.

The secondary function, by the long click, is the temporary hide of all points/tracks.

I believe this will be useful good enough, anyway let me know if ...

I can only guess, as you do, that it's something to do with the way the highways have been drawn. It's a whole lot better now that Mapsforge renders pathtext along curved paths but it's still far from ideal.
I think @Emux knows most about this.


Sent from my CPH2197 using Tapatalk

[new Beta version]

Enjoy the weekend with the new version on Google Play & new published new Beta version (with an improved map content panel).

@jonny.blue
uff 

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.

Hmm good point ... app currently supports local "pdf" files and external "html" links. So if you have a theme named "my_theme.xml", than app automatically searches for "my_theme.pdf" legend file. I'll improve this to the next app version and add also support for "my_theme.html" file.

Embedded images has a huge advantage: the display of such file is a lot faster because there is only a single request to download the file. Also, it allows using a theme embedded into the zipped theme. If there will be HTML + images, the legend in the "zip" won't work.

[@Andrew Heard]

@Andrew Heard
- error when clicking a legend: issue in the theme. Legend is in this theme defined over "lnk" file it should contain the relative path to the XML file (as I wrote for example here).

I'm thinking if I should fix this on my side (rather not) so suggest to @karlchick to fix it in the theme.

@Tapio
hidden tracks + visible track waypoints > I would like to stay with the current solution, because waypoints are directly connected to the track!

@T-mo
agree that hide points/tracks need some tweaks. I'm currently changing it a little bit ...

Bug > ah, thanks, will be fixed.