Web Planner route line customisation
Gathering feedback
I would like to edit the route line eg make wider and translucent so I can see what type of feature is under the route line.
This is useful when I have a lot of routes in my library and can get a better understanding of what surfaces are involved for each. ie so not so much in the initial creation but choosing a route from one in my library.
I like this idea 
Not just this, but also show track styles and allow editing of track styles just like it is possible to do on the App. Also, when syncing routes/tracks with the web planner and the app, the web planner doesn't show any of the colour/style customisations that were made in the app to the route or track.
Not just this, but also show track styles and allow editing of track styles just like it is possible to do on the App. Also, when syncing routes/tracks with the web planner and the app, the web planner doesn't show any of the colour/style customisations that were made in the app to the route or track.
Hi. Yesterday I have bought subscription after many years of using Locus Classic. I bought it because of planer. Now I see that I cant change the colour of tracks and all my tracks are gray. How to plan anything if everything looks the same. This thread has two years and still free planers are better than locus planer :/ (except cloud). I paid for this but i really consider to come back to classic locus and get rid of this planer. So dissapointed.
Hi. Yesterday I have bought subscription after many years of using Locus Classic. I bought it because of planer. Now I see that I cant change the colour of tracks and all my tracks are gray. How to plan anything if everything looks the same. This thread has two years and still free planers are better than locus planer :/ (except cloud). I paid for this but i really consider to come back to classic locus and get rid of this planer. So dissapointed.
Everyone, the issue here is most likely there isn't a web-specific version of the rendering engine the native app is using (mapsforge?) Hence, every more advanced feature will have to be reimplemented for the browser.
I'm not Locus dev, but i can guess this unfortunately will take some time to make it nearly feature complete vs. the app. And the reality is the subscription model is better to actually maintain constant work on the app (and webplanner too) than one-time payments for classic pro (albeit sometimes in the process they also break something i liked ;)
Everyone, the issue here is most likely there isn't a web-specific version of the rendering engine the native app is using (mapsforge?) Hence, every more advanced feature will have to be reimplemented for the browser.
I'm not Locus dev, but i can guess this unfortunately will take some time to make it nearly feature complete vs. the app. And the reality is the subscription model is better to actually maintain constant work on the app (and webplanner too) than one-time payments for classic pro (albeit sometimes in the process they also break something i liked ;)
Replies have been locked on this page!