Messages

Could you explain me how you connent to tasker? The only way I found was with Secondary Tasker App which is very limited.

Much easier way... And you can pass %par1 and %par2 into tasks just as in "Perform Task" command:

Code Select Expand

tasker://assistantactions?task=MyTask&par1=whateverArgument&par2={mapLat},{mapLon},{mapEle}

You may be interested... I'm sharing useful GPS related stuff up on Taskernet, eg. Pluscode, Latlon format converters, or a geopos calculator.

https://taskernet.com/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D

Dashboards vs. presets in todays new beta:
WORKS. Very likely. Thx Menion. Will observe. For every preset the dashboard had to be defined again in order to display the correct one.

Locus vermisst die alte Karte. Warum nur... Seufz. Ich hatte sie vorher gelöscht und die neue Karte erst im Nachgang konfiguriert. Locus verzeiht das aber nicht und bleibt beleidigt.

Konnte es nur fixen, indem ich die neue nochmal wegkonfiguriert habe (also preload global map: keine), dann benannte ich sie in die gewünschte j70 um, dann war Locus glücklich. Dann Locus beendet, die Karte wieder korrekt umbenannt, dann reinkonfiguriert, jetzt ist Ruhe.

Das ist mir auch hinterm Mond noch nicht passiert.
Ich vermute eher, dass Locus die Datenbasis fehlt. Ich weiß nicht, woher es die Ortsnamen nimmt. Entweder ein Webservice, oder vllt. Lomaps-Karten. Ich könnte mir letzteres vorstellen. Kannst ja mal eine ablegen, auch wenn Du möglicherweise OAM-Karten verwendest.

Dashboards in presets broken for me as well.

Still broken in recent beta. Presets only turn dashboards on or off. But they don't change which one is used.

Genau, Locus arbeitet zur Laufzeit mit einer Datenbank, die wird auch beim Backup gesichert. Ob man dann manuell oder automatisiert noch zusätzlich irgendwelche Zielformate wie GPX erzeugt, ist eine individuelle Sache.

@JackRussel, I was referring to <screenshot>, the action is called "Custom Setting", maybe there is something useful for analysis.

It is possible. I did some performance optimizations where this may be a side effect. If you find any steps to simulate it, it should helps a lot, thanks!

Seems like it may have been related to something else: I changed the line width of tracks on a folder basis, folder has 120 tracks which are visible. Locus applys it instantly, but displaying, zooming, dragging, map rendering stays very stuttering until I go to track manager, hide all, go to map view, go back in track manager, show all from folder again. Then it runs smooth again.

I searched for it for a few minutes. Didn't find. So my question would be: WHERE IS IT? I don't even know what to look for. Eg., I display geotagged photos, but there's no functionality to upload them.

EDIT: Aha I see now - Tap an online LoPoint and extend it with a photo.

As for terminology, what Viajero says, same preference by me. Imo the track editor isn't just fine-tuning. Fine-tune to my ears sounds less like a serious tool but more like "fiddling around", but I'm not a native EN speaker.

Btw any plans to allow undo/cancel save in track fine tune editor 😉? Changes there are instantly applied.

Screenshot and GPX attached. In the GPX, every TP has "<ele>10.00</ele>" - which Locus seems to misinterpret. I think not so serious, totally flat tracks are rather rare.

I always thought - what do you think - it's hard to spot what's an upper level, what is collapsed, what's expanded?

Totally agree converting/ promoting an ordinary track point to a Shaping or Via point is unnecessarily tedious at present. It's a very common use case. But we've had this discussion before right ;-(

Did we? Probably without Menion, because I feel he'd instantly agree 😁

Route Planner. I think the most common thing is inserting shaping points somewhere into a track- and this is a bit too hidden. First we have to go to the three dot submenu, pick "Trackpoint XY", then convert it.

I understand there's the same logic here as on tracks. You toggle between track segment and trackpoint.

The toggling to trackpoint should be bettom left, just like in normal track window. See screenshot - there could be a button "Trackpoint XY". That's my idea. Would follow the same logic as the track window.

Not following the logic, but ultra super mega convenient would be, if all three trackpoint commands ("Change to") were already visible in the orange screenshot area. Because why not - after toggling, the trackpoint screen additionally includes only Help and Streetview. Both are also available in the "Route segment" view. So you could unify and simplify it.

[What's the use case of this, how can this be useful?]

chg: improved system of generating shaping points for recorded/imported tracks loaded to route planner

What's the use case of this, how can this be useful? Just curious... I'd never try route planner on a recorded track. So now I did and it created shaping point #1 somewhere in the middle and some other shaping points somewhere.
So if Locus could algorithmically recreate a route from a recorded track (like BRouter web can do in "Load track as route"), that would make sense... but I don't see that on the horizon.

Re: PIP
Works now. Bug with increasing its size per tap. Last step makes it fullscreen just for a moment, then window disappears.