[APP] - version 2.19.X+ (updated 17.3.2014)

[KaHeMu]

In last versions I was grouping databases. It worked in pro and free version. But in 2.19.1 former defined groups are gone in data view. In selection view for exporting points groups are visible. In point description group info is missing too.

Regards,
KaHeMu

[Menion]

hmm so generally you miss defined groups in data > tab Points / Tracks?

I'm testing it now also on older 2.3.5 Android and it seems to work correctly. Think how to solve it ... some screenshots? Maybe better if you may share with me Locus/data/database directory?

[Bucky Kid]

I can see groups for points in data mamager latest version too. I however have one small wish, could the old Google zooming method be enabled per user setting, that means slide up = zoom in / slide down = zoom out. I somehow can't get used with the new style.

_____________
Sent from LT22i using Tapatalk

[Menion]

Hello,
  please give it a 14 days try and if after that time, you still not be satisfied with it, I'll create such settings. Because I had to follow same style as use Google Maps and that will most probably follow all other apps ...

[stebu]

Hello,
  please give it a 14 days try and if after that time, you still not be satisfied with it, I'll create such settings. Because I had to follow same style as use Google Maps and that will most probably follow all other apps ...

I think that Bucky Kid has a point. Now Locus behaves just opposite of Google Maps!

Now the upgrade 19.0 --> 19.1 went smoothly and even my dashboard survived it

[Menion]

are you sure?

locus 2.19.1 - double-tap and slide down - zoom in
Google Maps 7.6.1 - double-tap and slide down - zoom in

[stebu]

Yes, I'm sure, but my Maps version is 7.0.2.
I checked the latest Munzee app (it uses Google Maps) and to my surprise slide down = zoom in!

I have always "memorized" up/down with an airplane's control. Pull the stick towards yourself, the nose goes up and the scenery zooms out. I guess I need another analogy

[jusc]

I have to come back to this thread http://forum.locusmap.eu/index.php?topic=3716.0. POI names numbering depends how much different POIs are already in the used folder. (Locus pro 2.19.1)

[gynta]

about config.cfg

map_items_points_simplification_till_zoom

Locus set 10 as default - but described is 12

# allow define zoom level for points simplification. So value 14 for example
# means, that simplification may occur in levels 1 - 14. (default: 12)
#  - disable simplification at all: 0
#  - till zoom value (1 - 22 'include'): X
map_items_points_simplification_till_zoom=10

[Christian]

about labels and frames in config.cfg

Code: [Select]

# allows to define colors for labels. Where:
#  'bg' - background, 'border' - thin line around label
#  'normal' - not selected item, 'highlight' - currently selected item
map_items_labels_color_text=#0A0A0A
map_items_labels_color_bg_normal=#DCF0F0F0
map_items_labels_color_border_normal=#DC0A0A0A
map_items_labels_color_bg_highlight=#DCF0F0F0
map_items_labels_color_border_highlight=#DC960A0A
Thats pretty close to that i imaging Is there a chance to have "transparency" in bg? Then the problem with the hidden junctions behind the labels will disappear.

[gynta]

#RRGGBBxx
 xx should be the transparency
isn't it?

[Christian]

mmh, i'm not the specialist in coloring anything. How do "xx" have to appear?

[gynta]

Ah it's ARGB not RGBA
so try #26F0F0F0 eg

...and please post result 

[Christian]

Yessss! I tried it with RGBa but you did it right!
Thanx.

(read the f*** config header _before_!)

[gynta]

btw
@Menion

#00F0F0F0 works
but...
When Locus write back the config.cfg - Locus ignored "0".
So result is #F0F0F0

edit
google say:

Opacity %  -> HEX
00% ->  00
05% ->  0C
10% ->  19
15% ->  26
20% ->  33
25% ->  3F
30% ->  4C
35% ->  59
40% ->  66
45% ->  72
50% ->  7F
55% ->  8C
60% ->  99
65% ->  A5
70% ->  B2
75% ->  BF
80% ->  CC
85% ->  D8
90% ->  E5
95% ->  F2
100% -> FF