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 - joeloc

Pages: [1] 2 3 ... 21
1
Versions / Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« on: March 16, 2018, 16:48:32 »
I recently had Locus crash on me really hard... losing all settings and basically everything else. Fine I thought... doesn't happen very often really... I can simply restore the last Auto-Backup and be a happy camper again.

Imagine my surprise when Locus wouldn't even startup anymore... apparently because I had no internet?! Some weird stuff about initializing and downloading and "unknown problem code 10099".

Seriously?

Well guess what... I was on top of a mountain and in desperate need of Locus to backtrack my own steps through a glacier as the fog was rolling in. And there was no bloody internet for miles and ages!

So what's the story here? No internet, no Locus? Thats one of the biggest blunders I can possibly imagine for an outdoorsy adventure app. What if that crash had not happened in Europe but on one of my other trips... like in Peru or Bolivia or Nepal or Arizona or Godknowswhere? I might have been stuck with a stubbornly playing dead Locus for a long long time. Contrary to popular belief, you can still move around this planet for many days without the slightest bit of internet anywhere to be seen.

So what's so important that you absolutely need to download and cannot live without? I surely hope it's not a license check...

Can this be fixed? I really need to get Locus up and running again, even after a hard crash and without internet.





2
Versions / Re: [APP] - version 3.29.+ ( 1. 2. 2018 )
« on: February 11, 2018, 12:42:44 »
3.29.2... yet another release with training manager still making fun of every single mountain user... every single minute of every single day :/.

seriously... isnt this is a three minute fix? And if adding strings to the UI is really that complex, just remove

+ abs(altitude.loss)

from your code... which turns the thing into a thirty-second-fix. It's named "elevation gain" already anyway... and having a single correct gain value would still be a lot better than Locus current phantasy.

Please!

Long story again, just for completeness: Altitude gain and altitude loss are too very distinctive and very different things. Presenting them as one single value by adding absolute amounts is nothing but major nonsense... for any activity one can possibly imagine.

Thanks...  :)

3
since the forum seems to be mostly dead except the beta threads, i moved here:
http://help.locusmap.eu/topic/fully-automatic-track-and-waypoint-import-with-locus-actions

4
I want to import a huge amount of data into Locus automatically... around 50 track folders and 50 waypoint folders. I thought locus-actions could do this job and I already got as far as downloading. But then
<after>importData</after>
only opens up the user interface import dialog and waits for input. Not really that useful for automation with hundreds of items.

Is there any way to do something like
<after>importDataQuietly,foldername,create/empty</after>
// do not call the user interface but instead simply import into a given folder automatically, creating/emptying if requested

I assumed this to somehow work already, because otherwise locus-actions are a bit pointless for automated data import. Cannot find anything in the docs though.

Thanks,
joe.

5
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 16, 2017, 20:45:15 »
@menion, my google account somehow lost beta versions access... can't test the latest fix. But the last stable that you linked here for download does NOT have the Horizontal/Vertical problem. Everything works normally. So it must be something you changed between then and now.

6
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 15, 2017, 16:22:06 »
"Downgrading" Locus to a previous version has always been a bit messy for me. I have to uninstall the current Locus first, because Android 6 won't let me put an apk on top of a newer version. Then I can restore prefs from a backup, then the weirdness starts: The prefs "seem" correct, ie all the values in the settings windows are fine. Yet Locus will still use the defaults from the new apk installation . I have to enter each settings window manually and sort of click each settings item (not changing it) to make Locus actually use the restored Settings.

Just mentioning... not a major issue. Major issue is the horizontal UI I guess !:)

7
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 15, 2017, 14:06:36 »
There have to be something special on your device! There is many users with Note 4 and such huge problem will definitely cause a lot bigger response at least in comments on Google Play.

May I offer for now at least previous stable 3.24.3 version?
that one doesn't mess up the UI, but loses gps once every 5 minutes and never re-enables it until I do it manually.

.. guess I must abort the trip...

8
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 13, 2017, 07:00:26 »
Locus decided to be in German now... and the UI is messed up horizontally again. So maybe not related.

Many places are messed up... plenty of the lists are close to unusable because I can only see 3 or 4 chars of an entry.

This happens by itself after a few minutes/seconds, even without me ever rotating the phone horizontally. It never goes back to vertical layout, even when I rotate the phone around like a mad man.

Help!

9
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 12, 2017, 22:52:32 »
Hmm... Locus was set to English, system was set to German. Now I set Locus to system default, but it still comes up in English?!

The landscape problem seems to have disappeared for now though :)

10
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 12, 2017, 21:01:11 »
Landscape vs Portrait is correct... I also have this in many other places in Locus... like live tracking entry list eg. Rotating fixed it temporarily, but it *beeps*" up soon again after.

This only started like a week ago. Never had this before.

11
Versions / Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
« on: August 12, 2017, 19:08:15 »
I realize you're not the king of user interfaces... :), but the latest locus pro is utterly messed up for me. Somehow, the tiny map in point window gets besides the name instead of below or some such. Doesn't happen all the time, but at least in 50% of all cases. See attached pic.

Oh also... the search window is somehow too wide now... so the UI is invisible left and right.

All in all, new pro is reasonably bugged regarding UI. I wish I had backed up the old one :)

Note 4, Standard Marshmallow, no dpi hacks.

12
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 22:49:49 »
@joeloc , @slarti76 : what should I do to simulate this issue ( how to simply change DPI ), any app from Google Play?
Afaik, it's only possible to do this with root and XPosed framework - very Android-nerdy stuff. ;) For me, it's not important, and I don't think it's worth spending time on. There's much more important things...
Theres more important things indeed. I just thought maybe the bug is obvious... like using a different DPI value for cursor calculations/scaling and the rest of the UI. Testing will unfortunately require a rooted Android, xposed framework and the "app settings" module. Very nerdy indeed.

Anyway... Locus UI is just a tad small for moving bike-usage... but very well suited for couch-usage... or for while-being-stopped-usage. And I understand that the latter has preference and nobody really cares about moving bikes. It would be nice though if Locus had a simple "scale" setting that scaled everything at once... buttons... fonts... cursors... maps... just everything. Similar to what you accomplish by changing its DPI value with ugly hacks :).

13
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 22:40:24 »
Ok, guys, I will eat my hat and 3.24.xx is good. After some serious logging and emailing with Menion I found out that the track style on the map in combination with a quite big track, creates the slugginess I see at higher zoom levels.
Erm... I think I reported this bug more than two years ago... and menion already acknowledged the problem and did some profiling and blamed rendering code in Android. But basically, track styles were completely unusable since the beginning because they slow down Locus to a crawl (1 fps and less) at higher zoom levels. Since I quite often use high zoom levels to scout for campsites on sat maps, I had to stop using styles completely. Shame really, but cannot be helped until rendering is fixed, either in Android or in Locus.

A dead simple ten-second-workaround (also suggested back then) would still be:
if (zoom > X) style=0;

But obviously that would make more people complain about what happened to styles at high zooms. Performance isn't really such a big topic for most.. so what if rendering takes a second... or deleting track point takes five :-).


14
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 11, 2017, 08:39:52 »
Found the reason. I fake the DPI for Locus App to 620 (instead of default 540 on a Note 4). This works nicely to scale your UI (buttons and everything) to something more reasonable on a moving bicycle, but seems to mess up the cursor calculations somewhat. Weird, because all other parts in Locus scale absolutely fine.

@joeloc: hi ... hmm not sure where may be a problem. This is a "cursors zoro" right? I'm trying it scaled to 200% and it works as expected. On your screenshot is looks moved only few pixels. Center cross seems to be ok. Did you tried different set of cursors?
The GPS position (blue circle) no longer matches the center of the cursor image. No idea when this happened really, but I've been using cursor_zorro for years without problems.






15
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 11, 2017, 08:29:02 »
@joeloc: hi ... hmm not sure where may be a problem. This is a "cursors zoro" right? I'm trying it scaled to 200% and it works as expected. On your screenshot is looks moved only few pixels. Center cross seems to be ok. Did you tried different set of cursors?
The GPS position (blue circle) no longer matches the center of the cursor image. No idea when this happened really, but I've been using cursor_zorro for years without problems.






Pages: [1] 2 3 ... 21