[APP] - version 2.16.X+ (updated 25.10.2013)

[Menion]

b) is what usually comes in my mind, but problem here is in the lists .. what when you choose "select all" and then import and display on map? Hmm crash on note 2 at 60% (let's say about 1200 images), means crash on common devices at around half, maybe less. 500 images is still quite a lot, but it may happen. I agree that it's a problem. It's anyway a common problem in locus on many places. Just try to display (not import) more files and result will be same ... I'll think about it, thanks

EDIT: so expect this, rest should be fixed - hope - and it's available for normal usage in new test version

[ta-ka]

I've translated new texts at crowdin.net. I've also updated ja.tts.

- Don't you put prefix words like 'pref_gps_' or 'pref_guiding_' for newly created 'notify_*' texts?
- It seems that 'notify_next_point_desc' is missing.

Since there are relatively many new texts this time, could you please reflect the translations to the next test version? It is better to check them on the device before official release.

[joeloc]

b) is what usually comes in my mind, but problem here is in the lists .. what when you choose "select all" and then import and display on map? Hmm crash on note 2 at 60% (let's say about 1200 images), means crash on common devices at around half, maybe less. 500 images is still quite a lot, but it may happen. I agree that it's a problem. It's anyway a common problem in locus on many places. Just try to display (not import) more files and result will be same ... I'll think about it, thanks

This is probably not what you want to hear :-), but a search function for georeferenced pictures (including manual user intervention and super major delays) is a bit too old-fashioned anyway. That's how things were done ten years ago imho.

Nowadays, with a modern design, I would simply expect to enable the "local photo layer" with a single tap (just as a "panoramio layer" or a "flickr layer"). Everything else should be done by Locus behind the scenes... in the background... quietly... unobtrusively... automatically... without bothering me... without blocking the rest of the user interface even for a split second... without forcing me to go through "database-ish" search modules... without forcing me to watch "working..." dialogs for ages.

Of course this means more work on the programmer side. You'd have to play with the media scanner, keep a database with all positions up-to-date somewhere quietly in the background, rescan only changed files, update the map screen automatically when new pictures show up, etc. But in the long run, man hours spent on an uptodate software design will prove more useful than trying to speed up a somewhat old-fashioned search function that will always remain cumbersome to use.

Wouldnt it be great if a new picture simply showed up in Locus as soon as I take it?

[john_percy]

Parking in Locus POI database
Some maps get very confused with unhelpful icons for private parking appearing in many places. The standard Osmarender includes rules that say there must be either no access key, or access must be yes or public for the parking icon to show - see https://trac.openstreetmap.org/changeset/6939/subversion
a) The poi database for Locus ought really to follow that, IMHO
b) Locus maps ought really to follow that, too. Either implemented in the maps or the themes.

[Menion]

@joeloc: absolutely agree - not just do it

@john: thanks, will'll for sure look at it

I've planned longer vacation in September. It was anyway cancelled, so I'm leaving tomorrow on a shorted (just four days), so I've just published little bit improved version with some fixes. In next week, I'll probably publish it, so if there will be any problems, prepare for me nice list of work to do Thanks all!

[Bucky Kid]

Hi mention,
I think this is a minor bug of latest test version: when switching to vector map from personal map at high zoom level (18 and above), nothing draws. I have to zoom out/in to start map rendering.

Sent from LT22i using Tapatalk

[voldapet]

@John
Internal themes edited. But it's needed to generate new vector maps for full functionality (due to missing some tags)
Thanks

[john_percy]

@John
Internal themes edited. But it's needed to generate new vector maps for full functionality (due to missing some tags)
Thanks

Thanks for that.
Now here's another one:
With the poi popup, if the caption has an apostrophe (e.g. St Mary's Church) the popup has two (e.g. St Mary''s Church) - that's two single apostrophes, not one double quote.

[Ivo Nörenberg]

If distance to GPS in dashboard is 0, I would like to see a "-" instead of 0.0km. "-" needs less space so that you can see the map better. It is already so if you show e.g. track distance.

[john_percy]

Rendering issues
1. The street name for side streets starts in main road. This can be remedied with a "dx="16" in the style, or similar
2. One way symbol starts in main road. This I can't remedy

3. One way symbols get closer together as zoom level increases. The spacing depends on the particular road, however.

[jusc]

Hi John,

I tried it with my V-Scale Theme (http://forum.locusmap.eu/index.php?topic=3187.0). It looks quite diffrent. Maybe to less one way symbols. Because I can´t post a screenshot at this moment, can you please try it for your own?

[john_percy]

The screenshots in my post above were with Locus internal theme and Locus England map.

The ones below are from jusc's V-Scale Theme. Note the road name and one way symbol starting in the main road, but that there are far fewer one way symbols. This is due to the absence of repeat="true" in the line:

Code Select Expand

<lineSymbol src="file:/symbols/oneway.png" align-center="true" repeat="true" />
The downside is that there is only one arrow for each section of the road, and it can be obscured (see Salisbury Street and Lower Hester Street in the first image below).

[joeloc]

Btw... whats the exact problem with setting a custom language for Locus in Android >= 4.2? I think I have other apps that still do it nicely, just cant remember their names...

[john_percy]

Update on my post http://forum.locusmap.eu/index.php?topic=3423.msg24339#msg24339
I was mistaken when I said that it was connected with the uppercase transform. On my phone (HTC Desire S), the mismatch between the text and the outline depends critically on the zoom level, with zoom 19 being particularly bad.

[tommi]

Navigation / out of track notification is messed up:

1) Out of track notification = off vs. Settings of sound= disable:
Isn't that actually two settings for the same?

2) Navigation/Out of track notification distance vs. Navigation/Invalid distance:
Isn't that actually two settings for the same?

3) Nexus 7 hasn't vibration: can't store any setting in Navigation / out of track notification (doesn't accept touch on the set button)