[APP] - version 3.1/2.X+ (updated 4.7.2014)

[Menion]

@szebenyib: hmm, you know - if I'll not be able to simulate it, I'm also not able to fix it. So you will see.

@AndroidBubi: thanks, issue is unwated side effect of work on different project. Will be fixed in next "bug-fix" version at start of next week

[john_percy]

Following the latest update, it seems to me that stroke dashes now scale correctly in vector maps. Before the lengths of dashes and gaps shrunk as the zoom increased. Am I safe to assume this is intentional and will remain?

[Menion]

ah, I'm surprised ... because I'm almost sure I did no changes in MapsForge rendering . Interesting.

Are you sure, you do not changed any parameter because of, for example, this testing? http://forum.locusmap.eu/index.php?topic=4090.msg31285#msg31285

[john_percy]

Aha. It is indeed to do with locus-extended="1". Any documentation on this flag?
If I might rephrase my question:
With locus-extended="1" set in the render definition line, it seems to me that stroke dashes now scale correctly in vector maps. Before the lengths of dashes and gaps shrunk as the zoom increased. Am I safe to assume this is intentional and will remain?

[Menion]

Aha, yes . We created this parameter because we wanted to improve rendering for all locus themes, but also wanted to keep external themes to work as before.

So this parameter currently only change stroke in lines for every zoom as you found. So it's safe to use it. But keep in mind, that it's possible we change any other parameters in future that will be automatically influenced by this parameter.

[jusc]

@John,
can you please share an example? I don´t  understand. 

[john_percy]

I switched on "locus-extended" by changing the render line near the start of the theme to

Code Select Expand

<rendertheme xmlns="http://mapsforge.org/renderTheme" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://mapsforge.org/renderTheme ../renderTheme.xsd" locus-extended="1" fill-sea-areas="0" version="1" map-background="#f8f8f8">
The fill-sea-areas="0" avoids some unwanted artefacts with Mapsforge maps. It may well do more.
As menion says, it also makes the dashes scale in proportion on zooming in. Previously the dashes counterintuitively got smaller as you zoomed in. I used different values for stroke-dash-array at different zooms to counteract this behaviour. Now I don't need to, as long as I rewrite my theme accordingly.
For example I can replace:

Code Select Expand

<rule e="way" k="*" v="*" zoom-max="17">
<line stroke="#008131" stroke-width="0.7" stroke-dasharray="0,2,8,2" stroke-linecap="butt" />
</rule>
<rule e="way" k="*" v="*" zoom-min="18">
<line stroke="#008131" stroke-width="0.7" stroke-dasharray="0,4,16,4" stroke-linecap="butt" />
</rule>

with

Code Select Expand

<rule e="way" k="*" v="*">
<line stroke="#008131" stroke-width="0.7" stroke-dasharray="0,1,4,1" stroke-linecap="butt" />
</rule>


See how the proportions of the dashes change at different zooms in these screenshots using the Elegant theme

but not in these examples from my new Voluntary theme

It's much more significant where there are single lines of dashes for paths and so on.

[jusc]

Now, I understand. With this parameter my paths become very ugly.  Something more to do in the future.. 
Thank you for thi hint.

[CaptKaos2]

I updated to  Locus Pro 3.2.0 last night and today I was out Geocaching and had 2 random FC's when logging my finds.
The first was when I rotated the screen when typing, the second was on going back to a log and editing it. All other occasion where fine, and since my return home I have tried to duplicate it but cannot.
The phone state was in Aeroplane mode, wifi off, using Locus Bluetooth GPS and no other apps running. Hopefully it was a just a glitch, the next time I am out I will try again.

CK     

Edit Using offline logging setting.

[c.s.g.]

Using Locus Pro 3.2.0 I have a question about offline logging of geocaches.

I set "Einstellungen --> Geocaching --> Zeitzone berücksichtigen" and the corresponding timezone to "GMT +02:00" in earlier versions of Locus Pro..
If I do so in the offline logging dialog the suggested logging time is 2 hours ahead of the actual time!?!?!

In earlier versions of Locus the suggested time was correct!?!?

Is this a bug in Locus Pro 3.2.0?
Or are the setiings I have made obsolete for Locus Pro 3.2.0?

c.s.g.

[Christian]

Thanx for "reverse track". Its a long wanted feature.
Why it is only available in map with displayed track and not in track manager also? And btw. : if a track is copied within the track manager, the suffix "- copy" is added automatically. Why is there no possibility to copy the track to the same folder?

Anyway. Thanx a lot!
Christian

[Menion]

@CaptKaos2: best way for report FC issue, is log or a way how to reproduce it

@c.s.g. : thanks, I'll fix it. Issue on my side.

@Christian: 'copy to same folder' - I used same function as for move, where it make sense. Anyway why not - added. Just in case, you'll copy into same folder, Locus also adds 'copy' to end of name. 'Reverse' is available also in track manager, you just have to open track detail screen (simply tap on track in list)

[Christian]

Many thanx menion!

[Menion]

hehe, sure, you're welcome

[ta-ka]

Hi Menion,

I found that, in providers.xml, <serverPart> + {s} parameter for type=5 maps doesn't work.  On the other hand, it works for type=0 maps. I'm sure that {s} for type=5 maps worked before but I don't remember the last working version. Though it's quite minor issue, could you please check and fix it with attached providers.xml?