Messages

Hmm... Locus team must be preparing for star wars... 
Please check phrases of the app initialization at crowdin.

Hi menion,

> wear, analyze, altitude
Thanks!

> import dialoge
Yes, it's tiny thing. Anyway I reported it because I noticed

- Please see first image. The phrase and context of uphill and downhill are confused at crowdin. Translated anyway

- The phrase "Analyze..." (context: analyze) is shown while gpx/kml file analysis is actually going on when impoting. So, please don't reuse it for solid menu/title name of track analysis feature. Please add a new word dedicated for that.

- In the point basic info screen (see second image), the title of point's height is 'altitude' but it is 'elevation' in edit screen. Could you unify both of them with 'altitude'?

- When you add a new point with the same name of already existing point, the dialogue with the hint phrase "Press 'Ignore' to import with the same name anyway" is shown.  But user is adding new point, not importing.

   

Hi luxcalor,

Custom icon packer is a bash script. It means that you need Linux system (or similar) and have to work on command-line interface. Do you have working linux system with you?

If you use windows only, installing Ubuntu on top of Windows from Windows Store should be the easiest way to have linux system. Ubuntu is one of the popular Linux distribution and officially supported by microsoft since Windows 10 Fall Creators Update. Try net search with the phrase 'How to Enable WSL in Windows 10 Fall Creators Update', you will find several installation instructions.

When you have got ubuntu working on your PC, I'll explain next step.

@ta-ka: thanks, agree, I've added it also to this new editor, thanks

Thanks for improving to show the recorded time of the track point in route planner.

3.24.14 RC
new Route planner and Track editor switched to old good system (for next release)

I look forward to test it with next beta after stable release.

Hello menion,

I would like to ask one improvement on 'Modify track' while editing recorded tracks.  Could you make to show the recorded time of the selected track point on the edit screen? For example, there is a enough space between track point name and (i) icon for that as shown in the first image.

Reason:
When I determine the point to apply edit command like 'cut part of track', 'split' and etc..., I always take into account the recorded time of the track point as well as the position. With the conventional 'Edit on map', the recorded time of the track point can be directly seen on the map screen, as shown in the second image. (Settings > Maps > Points & Tracks > Tracks popup content > 'Distance to GPS, Recorded time' have to be enabled). It is very handy to determine the exact track point because by simply tapping forward/backward track point button, the recorded time of the next/prev point can be flawlessly seen on the map screen without opening track points detail screen.

   

[Google Earth Icons/Pins pack]

Google Earth Icons/Pins pack

1. Download 'google_earth_icons.dat' and 'google_earth_pins.dat'
2. Execute custom_icon_packer command
    % ./custom_icon_packer google_earth_icons.dat
    % ./custom_icon_packer google_earth_pins.dat
3. Copy created "Google Earth Icons.zip" and "Google Earth Pins.zip" to Locus/icons folder on your phone/tablet.
4. Have a fun!

I release an easy to use bash script to create custom icon pack for Locus Map. Based on a simple format definition file 'info.dat', it's possible to:
  - download icons from internet.
  - generate info.xml with favorite icon listing order and icon categories.
  - create custom icon zip archive.

Created icon pack is compatible with Locus Map 3.24.1 and later.

If you share your custom icon pack which may contain copyrighted icon images, just share definition file 'info.dat'. As it only contains icon image URLs, sharing it won't violate icon's terms of use. Users can download, pack and use icons on their responsibility.

Related Links:
- http://docs.locusmap.eu/doku.php?id=manual:advanced:customization:icons
- http://help.locusmap.eu/topic/own-icon-pack-icons-divided-into-groups
- http://help.locusmap.eu/topic/custom-icon-listing-order-in-icon-chooser

Hello. I've got two issues with version 3.23.2.6.
- Locus fails to get weather info with 'Bad Request code:400' if language setting is Japanese.
- Two finger measurement: On android version 4.4 and 4.0.4, magnifiers and pink circle are not shown but only pink line and measured value are shown.

@ta-ka: thanks, I've found another places where units were not set correctly, so let's try another round ...

Hi menion.
hmm... the issue is still there with 3.23.1.5. I noticed that the line width of the 'Line to GPS' is thicker as well.
It might be device specific issue because I see those thick width lines only on LG G3 valiant device with stock Kitkat (4.4.2). I didn't provide device info before. sorry for that.

Nono it isn't. There is only hidden "mess" in sizes for various lines that needs to be united . As I see, here is width incorrect, I'll fix it, thanks.

Please also check the width of the line from last added point to map cursor while 'Add new route & measure'.

I want to remind tts translators that tts files on google drive has been (silently ) updated to version 6. (or did I miss announcement?)

Hello, lor74cas.

For training voice (and navigation voice), phrases have to be defined by tts file for each language. To prepare tts file for italian, download en.tts from google drive, put it in Locus/data/tts folder, and just rename en.tts to it.tts. The link to google drive is written here http://forum.locusmap.eu/index.php?topic=3227.0.

Then, in Locus 3.21.1.19, set both 'Language' and 'Text-to-speech settings' to italian, and start training. You should hear 'Ritmo bla bla per kilometer'. Actually I've confirmed that.

Now, you can edit the english phrases into italian and when you complete them, upload your it.tts file to google drive. It will be embedded in next version of Locus and Locus/data/tts/it.tts file is no longer needed.

Hi, menion.
I've updated ja.tts for v5 (24.2.2017).  Please confirm and fix followings.
en.tts: parameter for 'value_speed_avg_interval' and 'value_speed_avg_track' should be "%V1" but not "%D1".
README.txt: 'value_day_time' -> 'value_time_current'

Hi, menion.
I agree with your decision. Have you updated en.tts in google drive yet? And don't forget to replace indent spaces into tabs.

@menion: I don't know why but it seems that leading spaces in tts file cause a problem. I replaced them with tabs and it works.