Messages

To menion:
Here's another ugly bug with route planner: opening it on certain track forces Locus close. I'm trying to figure out what's specific with this track that it makes Locus crash.

Record from the error log:

Code Select Expand

03-22 13:42:01.281 17089 17089 E AndroidRuntime: FATAL EXCEPTION: main
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Process: menion.android.locus.pro, PID: 17089
03-22 13:42:01.281 17089 17089 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{menion.android.locus.pro/o.sl}: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2699)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2766)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1507)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6236)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.util.ArrayList.get(ArrayList.java:411)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.azp.ॱ(:78)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.iq.ˊ(:705)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ॱ(:2478)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ˎ(:2433)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:604)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:210)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˊ(:77)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Ч.ॱ(:166)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.ҫ.ˊ(:129)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Cz.onCreate(:63)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sl.onCreate(:161)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6684)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2652)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: ... 10 more
03-22 13:42:01.289  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/o.sl
03-22 13:42:01.300  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/com.asamm.locus.basic.MainActivityBasic


All panels are preserved for me in 3.30.1

Which nightly build? Last updated yesterday at Google Play, my settings are preserved with that build.

That is weird. Please try to import this track and move point #24 anywhere.

@meinon: have you taken into account the blind turning?

Hello, I've found a broken behaviour in track editor
Changing of track shape is unsuccessful + following Locus behaves as route planner without routing outside any mode. Please see the screen capture

https://photos.app.goo.gl/DHeo5znrlmmeiR992

________________________
Sent from my phone using Tapatalk

A new Brouter version is here

brouter_1_4_10.zip(current revision, 07.03.2018)

fixed motorcar TR exceptions

added vr-forum profiles to distribution

added suspect manager to RouteServer

polygon nogo pull request (QMapShack)

nogo encoding pull request (QMapShack)

http://brouter.de/brouter_bin/brouter_1_4_10.zip

________________________
Sent from my phone using Tapatalk

Here's a minor bug:
If Locus left in background with opened route planner to terminate by system, on next launch opens directly to route planner, but maps not initialised (blank).

________________________
Sent from my phone using Tapatalk

Just tested and it works as expected

graphHopper 0.11 is now the snapshot

Hello menion,

You guys are building own APK add-on? Is current project on GitHub works without problem for you? Better asking: is a current structure on GitHub clear and easily re-usable now?

the answer is no and no (see previous post by me). Current nightly updates can be (or not) preparation for 0.11 snapshot, anyway current gH sources generate routing data not compatible with latest official plugin. But it may be good to wait for next stable snapshot (as there may be more compatibility changes)

Here's latest data for test:
https://drive.google.com/open?id=1rwnMx3RlRIdMZKGbOExtj4dR85MOt4ti

With silent update from 18/02/2018 on github, Locus plugin is no more compatible with generated routing data. Can anybody confirm or mistake on my side? I build the sources using latest JDK and Maven.
The engine is still 0.10-SNAPSHOT but not working with plugin 0.4.2 anymore.

@menion: I use fullscreen view since 4" screen on ICS and honestly never had a problem with it. If you plan to add bottom buttons permanently visible, please make it per user preference.

________________________
Sent from my phone using Tapatalk

Jde to tak
Vůbec mě nenapadlo že se barevný mód aplikuje na samotný vzor. Díky, vyřešeno.

@sundsval
Jestli máš na mysli průhlednost jak je vlevo

tak ta už v nových verzích není možná. Pokud jsem pochopil jak teď funguje vzorkování trasy, trasa je kreslená do mapy jako plná čára s vlastní průhledností a vzorek ze kreslí nad trasu taktéž s vlasní barvou a průhledností , která ale nemá vliv na průhlednost trasy.
Taktéž bych uvítal možnost vykreslovat přerušení postaru, ale to by se musel opět předělávat způsob vykreslování.