Locus Map - forum

Support => Troubles & Questions => Topic started by: gynta on July 14, 2012, 18:57:20

Title: config.cfg
Post by: gynta on July 14, 2012, 18:57:20
what means: "draw labels only since defined zoom level (always: 0, from zoom value (included): 1 - X, default: 0)" ?
which labels? there are several
Title: Re: config.cfg
Post by: Menion on July 14, 2012, 19:38:56
this is for labels that you get  when you move map center over any point on map. Small white labels with black text and black border. You may limit drawing of such labels only since some higher zoom levels ..
Title: Re: config.cfg
Post by: gynta on July 14, 2012, 20:10:49
hm,  i set this to  "1 - 12"  and i wonder because thats has no effect :roll:
I have misinterpreted the description
Quotefrom zoom value (included): 1 - X
I thought, "1" is switched on
and then "- 12" for the  zoom level

now it works
thx for reply
Title: Re: config.cfg
Post by: gynta on July 15, 2012, 00:07:10
a wish/idea:
(maybe the wrong place, but i dont like to open a new topic)

Quote...
# Utils
# --------------------------------
# display notification Toast message when duplicate folder at start is detected (enable nofity: 1, disable: 0, default: 1)
notify_duplicate_root_folder=1
# set speed for moving cursor on map when GPS is off (in m/s) (value <= 0 disable this feature, default: 0.0)
speed_for_moving_cursor_when_gps_off=0.0
# separate NMEA records. Every record will have incremental number during one day instead of one big file (enable: 1, disable: 0, default: 0)
separate_nmea_records=0
# delete logfiles that are more than xx days old (delete nothing: 0, keep for XX, default: 30)
keep_log_days=30

...
maybe you can do this during the startup  process
because i found 25MB in last 2 month - not much, ...but in 34 days :roll:
Title: Re: config.cfg
Post by: Menion on July 15, 2012, 07:56:19
25MB? :) I'll probably delete this logs system. It was useful long time ago when there was no reporting on market, no such nice app like CatLog etc. Also such error aren't much useful. When Locus crash on any serious error, these files usually do not contain last information, so they have no benefit.

I saw some new mechanisms for automatic error reporting so I'll later check any of them. Thanks for pointing me on this "problem"