Set default "Valid for" from providers.xml

Hello Evgeny,

thanks for the idea, make sense, implemented. Will be added in 3.40 version (most probably middle of September).

Menion

I saw "validFor" in changelog. How can I test it?

"<validFor>2</validFor>" inside <provider> it seems doesn't work in last beta - I always see "0" in "Set 'Valid for'" dialog.

Ah I'm stupid. I see the issue now.

Next Beta. Sorry :).

In last beta (3.39.4.4) For validFor>=2 - everything is works fine. But:

validFor=0 - in map info: Can be cached = Yes, Valid for = unlimited

validFor=1 - in map info: Can be cached = No

And if I set something in "Set valid for" dialog - I can't delete it (to return to default, defined in providers.xml) - it say "Field cannot be empty".

And may be it's usefull to see default (from providers.xml) valid period in"Set valid for" dialog?

Ah, good observation.

In case of value "0", this value was ignored when supplied from XML.In case of value "1", it was used correctly, just incorrectly visible state in UI.

Generally, the usability of this parameter is really terrible as I see it. No known default/max value, unclear setup of new value etc.

I can imagine a lot better UI, but because of it's low importance, let's improve what exists. So these two issues are fixed now, thanks.

As the most simple solution, I've added maximum allowed "valid for" value into detail of online map (in case it differ compare to current value).

Menion

Yes, you'r right: it's low importance feature.

But:

- how I can clear value in "Set valid for" dialog? (to return to default from providers.xml) Now I can't save empty value.

- in current implementation, validFor from providers - it's "designed maximum"? :( I think, this should be only default, but user can redefine it in "Set valid for" dialog to _any_ value - greater or smaller.

Understand,

Clear value: in next version will be possible to set empty "edit field" which reset the value to default (maximum) value

Changes in next Beta/release

• cacheTimeout - set "users" defined "valid for" value
• cacheTimeoutMax - set maximal possible "valid for" value

Colleague Michal wanted to rename it so in next version, this will be called "Cache timeout" instead of "Valid for".

<cacheTimeout>5</cacheTimeout>
<cacheTimeoutMax>10</cacheTimeoutMax>

Locus 3.40 RC1.

Example xml attached.

P.S. It's look like, in current beta-version interface language switch doesn't work - Locus always showing in Android system language.

Hello Evgeny,

I'm often surprised by the patience of users, like your in this case :).

So next try, next version. Thanks.

It seems, everything is ok in last beta!

Thank you for patience too :)