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.

Show posts Menu

Messages - Tapio

I found no way to make icons working. E.g. absolute path: "file://storage/emulated/0/Android/data/ L_hscc.png"
Quote from: Andrew Heard on Yesterday at 00:35:28@Tapio maybe a little Tasker demo project to share?
Sure, demo task. Please test the icon part as Menion suggested, haven't done yet. Also haven't tested the map move commands.

Menion, would a database path attribute be possible, so we could directly implant points into the database? Would open up for great possibilities.
Quote from: Menion on July 19, 2024, 15:12:18I've just created it, sorry not to write this. It will be available in the next Beta version.
New beta... It works! The naming works, but icon does not, or I don't know how. I used "icon":"Z-ico02". The icon name I retrieved via longtap an icon.
This new intent is super interesting, a hidden gem? but I can't make it do anything. Nothing happens in LM.
If this method would allow for putting stuff directly into the db, that would be gold.



data:{map_point:{"name":"test", "icon":"Z-ico02", "lon":8.9999, "lat":50.9999}}


Broadcast Receiver
Quote from: slarti76 on July 15, 2024, 11:37:29I find it a little weird that two people thank you for a post basically telling me my bug report is of no importance? I don't complain when others report bugs that are of no concern for me...
Nah..., not about importance, just target audience. I apologise, my post was a bit unclear. I'm rather thinking this kind of stuff should better be handled via an official ticked because there's likely nobody to address in the user forum.

Out of curiosity - why do you use these kinds of maps instead of OAM/Lomaps?
Well, do you really think there's another person on earth using orux maps in Locus?
Legenden sind abhängig vom Theme.
Themes - Vector maps / Re: [Theme] Tapiola
July 13, 2024, 11:06:42
Hi, red are generally access = private, restricted etc. - Should probably be respected by hikers and cyclists.
Yes, blue is restrictions only for bicycle. Color may change a bit but will be blue.

It's by far not perfect, I'm not yet handling overlapping cases and all kinds of tags. Will properly review the cide. Elevate is more sophisticated there.

There's an interesting "political" aspect to restrictions "foot=no", I've read discussions about it. The german OSM community is master @ discussing at biblical length.
Eg. paths in forests where mtb cyclists don't want hikers, thus put foot=no into osm.
Themes - Vector maps / Re: [Theme] Tapiola
July 13, 2024, 10:13:47
Quote from: Mick FU on July 12, 2024, 20:49:47My screenshots are taken from here
47.70386323, -3.19546355
A quick change is in the xml on Github, please try it (replace Tapiola.xml inside the zip).
If you find more problem positions, let me know.
Michael Bechthold hat doch hierzu mal eine Menge geschrieben, meine ich jedenfalls... wenn das jemand findet (ich fand den Post nicht). Müsste mal dringend angepinnt werden.
Themes - Vector maps / Re: [Theme] Tapiola
July 12, 2024, 19:18:16
Thanks, will investigate. Probably some tag missing, "access restriction indicators" is indeed the right option. Please give me a position.
My main perspective is hiking. The restrictions are quite tricky, different tags are used, some restrictions only for specific activities... not fun 😁
Um 12 Uhr: "Wegpunkt Baby, iss die Banane, 11 Uhr" könnte missverstanden und bildGRAV verhungert - also Vorsicht!

@bildGRAV Ein paar Punkte setzen und diese ansagen lassen ("Point alert", sorry, meins steht auf EN) - so mache ich das manchmal auch. Lasse mir ansagen, z. B. dass eine Pause empfohlen ist (und ich halte dann Ausschau nach geeigneter Stelle), oder dass gleich eine schwierige Stelle kommt, dass das schlimmste vorüber ist, Bergfest km, Bergfest hm, etc.

Auch nützlich in diesem Zusammenhang: Wenn man geogetaggte Photos angeschaltet hat und da schon mal war. Diese werden angesagt. So kann man dann ein Bild an der gleichen Stelle ein paar Jahre später machen. Deswegen bin ich auch so da hinterher, dass die Anzeige der Bilder mal besser wird, ist leider noch nicht gelungen. Die Vorschau im unteren Panel schreit förmlich danach, auf Bildschirmbreite gestreckt zu werden, die Adressinformation ist in dem Kontext "Fotopunkt" irrelevant und muss nicht direkt sichtbar sein. Wenn man irgendwo im Wald steht und einen Fotopunkt antippt will man das Foto genauer sehen und nicht einen Strassennamen. Screenshot.

Beachtet den Dateinamen des Fotos, die sind alle so umbenannt, dass die Ansage sinnvoll ist ("DCIM1234" ist weniger praktisch).
I had a different crash and sent log to Menion. CTD after adding several shaping points, BRouter classic. Just fyi.
Quote from: Menion on July 03, 2024, 10:45:15a) I'm not aware of any change that should affect this. Are you using only a tasker for this right? I'm asking if there is an identical problem with any other app ... always an identical indent (except coordinates of course)?
I've put together a simple profile which reflects what it's about. This one creates a random position around you, every 100s (the Tick trigger, 100000ms) and gives it to LM4.

My problem: this runs in the background. Very often I unlock my phone and find LM on top, staying in the loading screen.

Note I use "Launch app" plus two intents.

- Without LM started beforehand, the intents don't tend to work. In the past it was different
- The Locus Action intent moves the map without animation. It cannot create a temporary point.
- The geo intent can not move map without animation. But it creates the temporary point.
Menion, Intent via geo:lat,lon... Since 2-3 beta versions I observe a):

a) if Locus is started this way, very often it stays in the starting screen with the logo. I have to tinker then, go back, start again...

b) I send many points via geo:lat,lon in rapid succession (from a Tasker array of positions). I wish it wouldn't move the map smoothly, but instantly. Or even better, not move and center map at all, just add the temporary points. Can you make this possible? The Locus action "map_move_zoom" has the property "animate:true/false", but I cannot use this action because it creates no temp. point.

Has there been a related change?