Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - 0709

Pages: [1] 2 3 ... 14
1
Troubles & Questions / Re: Create shaping points?
« on: April 20, 2018, 22:48:25 »
The Garmin file: A gpx (rte) route ? Pse confirm by sharing (a) short example file.

Garmin (rte)route: Garmin Via or Shaping Point difference is visible in the looooooong extension.
Garmin Shaping Point is a Via Point not announced by sound nor Icon by SOME Garmin gps devices.

http://www.poi-factory.com/node/45244  See second post by johnc.

Function ‘sound muting’ and “Icon hiding” of the Garmin Shaping Points is not supported by Locus.

A Garmin route(rte) imported into Locus !
Both Garmin (rte)route Via Point and Shaping Point are announced by sound and Icon.

Locus track_navigationwaypoints (trk_navwpt)
Locus Via Points are announced by sound and Icon. (Sound TTS = by <name> and Icon = by <sym>)
   
A discrete Locus Via Point: <name>= empty and <sym>= Waypoint.
No TTS announcement , a discrete mini black dot Icon, still functional (auto)recalculate.


Garmin (rte)route shaping points are different from shaping points as used in Locus map.
Locus Shape Points
Have only temporarily use in the Locus routeplanner (database)
At navigation: No announcement no Icon no autorecalculate.

@Menion.
The imported (rte)route by the routepoints extension shows up in Locus with correct shape (follow streets) inclusive the Via Points by origin Basecamp router. No NavPoints, how to add ?
By the BETA version only ! By long push recalculate button in the routeplanner results in a (re)design with the Via and Nav Points.

Example in attachment. (Has one Garmin Shaping point)

2
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 17, 2018, 10:08:33 »
I understand this msg probably was lost because of more  important previous gps problems  :)

Gesture functionality by the proximity sensor in landscape modus.

During succesfull (portrait) proximity gesture session. By any map switch to Landscape mode the gesture function is lost ! No function recoverey unless by reactivating (in portrait mode !) the screen on/off control.  (Tested and repeatable issue on both Samsung and THL phone). (A 4.4.2)


3
Troubles & Questions / Re: "Track has re-calculated" loop
« on: April 16, 2018, 14:28:28 »
The trick is to NOT add medium waypoints!    Create a start point, then move long your chosen path placing an "End Here" marker at each point, progressively moving it along.  Not intuitive at all, but it works fine.  It also works fine for Locus.

Can you share  a (short) demo design by kml file ?  tnks.

4
Troubles & Questions / Re: "Track has re-calculated" loop
« on: April 16, 2018, 09:09:26 »
I tested a kml file from Motogoloco design by adding medium waypoints between start and finish. 
No optimal klm out as the waypoints are inserted as wpt_poi, not as necessary (router) Via points.
Locus_Brouter autorecalculate to point directly navigates to finish, thereby skips 'medium' wpt poi's.

Need some usefull Locus tips ?
http://www.locusmap.eu/news/
http://www.locusmap.eu/news-version-3-26-0/
http://www.locusmap.eu/how-to-set-alerts-for-leaving-your-navigation-route/

5
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 15, 2018, 09:26:55 »
Quote
I have no time
  ?  8)
For me, backup function for both Locus Pro and Free (beta) is ok and fast.
Pro and Beta (TESTS running !) my settings are mostly slightly different.
Before Locus Free (Beta) update manualy backup last used settings.
After install restore. Eventually a restart. No problem.

7
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 11, 2018, 20:10:07 »
Navigation > Advanced settings > Snap to route: Unselect ?
In picture: Navigation is not finished ? (Final point).
Other advanced settings same as before ? (Max allowed deviation)
Did you compare with your succesfull 3.30.2 pro settings ?
 

8
http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:navigation:settings#auto-recalculation
+ See attachment pdf  (Settings I do use:  Out of route alert: 75 m  Autorecalculate: 100 m.)

10
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 03, 2018, 14:35:38 »
Picture helps ?  See pdf.

11
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 03, 2018, 11:33:12 »
New Android Samsung versions with same issue in Locus by default (country specific)system language? A volunteer for a test and a report ? 
Hack ? Locus map menu does not select the Android default system language.
Quote
do not know what may be a problem
The language select indication in the menu is correct but the Locus menu result is false. Locus Store: (the translated [NL] folders menu) do recognise the Android system language.)
- Double checked by other app "Gpx viewer": App menu by choice system language is ok.

12
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: April 02, 2018, 20:18:00 »
(Language switch was functional by older Locus Versions in A 4.4.2). 
Locus V3.30: Language: Select the app language > msg: "This function requires Android 5.0 or newer"

Result in [NL] TAB4 tablet: Locus = English while Locus indicates = [NL] language ? (NOK)
Restart hardware does not solve. Locus Store is [NL] correct.

Result in [NL] THL4000 phone. = Correct [NL] Locus. (OK)

EDIT !
Language (android) setting;
THL4000 
> Nederlands > Locus = Nederlands (OK)
(Keyboard layout = Free Set)
Samsung TAB4:
> Nederlands (Nederland) Samsung Keyboard Nederlands = qwerty (OK) > Locus = Nederlands (OK) 
> Nederlands (België) Samsung Keyboard Nederlands = azerty (OK) > Locus = English  (NOK)

More:
Deutsch (Deutschland/Österreich/Schweiz).
> Deutsch (Deutschland) > Locus = Deutsch (OK)
> A / CH > Locus = English (NOK)

13
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: March 31, 2018, 20:58:40 »
Long push settings.
What is experimental mode enabled or disabled ?

14
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: March 25, 2018, 14:54:29 »
To prevent any mistunderstanding, my +1 was only about the UI suggestion ! 
By keeping the cancel/save button visible no need to dismiss the keyboard
(Covered cancel/save button: For a new Locus user, it might be a small pitfall)


15
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: March 24, 2018, 10:42:40 »
+1
Quote
A logical thing that would resolve this trap as well as the button thing were to put the save/cancel buttons to the top of the edit forms. That works for any device, smoothly.

Pages: [1] 2 3 ... 14