Messages

regarding "data" pancake floppy disk madness. two things are important:

for beginners: give them icons that actually look like the functions they represent. points, tracks and layers. google (eg earth) call your "elements" function "layers", you should do the same and also use a similarly looking icon.

for pros: when i click the track icon, locus MUST take me back to exactly(!) where i was when i left the track list last time. same for points.

how you arrange it "internally", ie completely separate or within a tabbed view like now, does not matter much imho. I would like to swype left and right to change tracks though. And it would be GREAT if they looked pretty and were simply editable in place right away instead of going through another (pointless) edit function with another (confusing) view of the same data.

With latest Locus I keep seeing an orange OVER_QUERY_LIMIT almost constantly. Why is that? What is "over query limit"? How can I avoid it? Your error messages could really be slightly more detailed...

Voice navigation does not work at all for me in latest Pro. I could only once select a voice with that Locus function but nothing happened. All further tries to select a voice simply do nothing. No selection window appears. Andro 4.1.2. with ivona voice installed. Google maps voice nav works nicely, as do all other voice apps (eg ebook readers).

To walk this way further I propose (like some others) to drop the "Data" layer of menues - this again is a pure technical category (as you store these infos in databases).

I couldnt agree more. A GPS program that doesnt have Points and Tracks in the very first(!) UI layer is mostly useless to non-geeks.

Mummy: Where are my waypoints?

Me: Look here... your waypoints are hidden behind this funny icon that looks like a few pancakes and a floppy disk.

Mummy: What is a floppy disk?

Me: Something weird that was used twenty years ago, dont bother.

Mummy: But what does this floppy disk and those pancakes have to do with my waypoints?

Me: To be honest, I have no idea. The programmers seem to think that this is a bright idea and they stick with it since years. Internally, they store certain things in so called "databases" and this is probably what this icon represents.

Mummy: Can you give me another icon that actually looks like a waypoint and simply takes me to my waypoints?

Me: Sorry, not possible with this App.

Mummy: But isnt clicking on pancakes and fluppy desks a bit silly if I want waypoints?

Me: Yes.

Mummy: Can you install another app with icons that actually do what they say?

Me: Sure, just a second...

To be a bit more productive instead of just whining, I just drew a mockup of how a unified track info & edit view could look like:
https://getsatisfaction.com/locus/topics/unify_track_information_and_track_editing_in_a_single_view?rfm=1

*That* would be a change worthy to be called "big GUI rewrite" :-). And just imagine how many menus and buttons and other stuff you could simply remove from current Locus...

> changes:
> - big GUI rewrite

really? i had serious hopes after reading this, but none of the major blunders were even remotely adressed :-(.

1) database manager nonsense screen: besides of it being completely counter intuitive for non-geeks, it prevents locus from remembering positions in track & points lists and forces us to re-open categories and scroll through long lists EVERY SINGLE TIME we deal with tracks .

2) splitting of track/point view & edit screens. seriously... why in gods name are you doing this?! having ONE SINGLE track view with editable fields would get rid of so many useless buttons and silly complexity in your interface.

if those points arent even addressed in a "big GUI rewrite", i guess keeping up hopes is kind of pointless.

Here is a possible track VIEW AND EDIT screen:

Menion: "Data manager screen is in preparation"

It should be ON ITS WAY TO HELL instead . This is one of the super major user interface blunders in Locus since day one. How long will you consider your users to be database administrators? Hint: They are not!

- please, all (joeloc mainly) who had some problems with map loading, try this version

Been trying for quite a while now and cant seem to reproduce the missing tile problem any longer. Neither on rmap nor on sqlite. Good job :-).

I tested with the World_OSM map, but can't confirm the problem with Android 4.1.2 and a 32GB Fat32 card.

And I just bought a new phone (Galaxy S3, Android 4.1.2 Samsung Stock ROM, 32GB Fat32) for somebody else and put a fresh Locus install on it. The problem is exactly the same: tiles disappear

And just now I updated the Note 2 to Android 4.3 (XXDLK7) and can reproduce the tile problem easily. That is on a completely virgin installation with nothing but the ROM and Locus.

I tested with the World_OSM map, but can't confirm the problem with Android 4.1.2 and a 32GB Fat32 card.

And I just bought a new phone (Galaxy S3, Android 4.1.2 Samsung Stock ROM, 32GB Fat32) for somebody else and put a fresh Locus install on it. The problem is exactly the same: tiles disappear

The missing tiles problem also happens with this tiny (400MB) orux-format map:
http://www.openandromaps.org/maps/world/World_OSM.zip

With this map, the tiles just remain "empty". There isnt even an "unknown problem" text. And yes, I believe it is triggered by scrolling immediately after zooming, something that happens frequently when using two-finger-pinch or double-tap-and-hold.

"cannot read image"? maybe also a file io problem? maybe too many open threads that try to access the rmap file at once? Maybe too many file descriptors? I think I have read somewhere that Android up to 4.1.2 is limited to 1024 file handles in total (ie system wide!).

https://code.google.com/p/android/issues/detail?id=39002

cant you at least show the x,y,z values in the error string for the tile? and all other information you have? file handle pointers etc? i'd really like to use new Locus as well, but the problem is annoying enough that I had to downgrade. it really happens all the time here. not just when trying to force it, but also during normal usage on the bike.

[@joeloc & @buckykid]

@joeloc & @buckykid - I've just copied almost 4GB big RMAP, and still no problem. I've played with it more then five minutes and no even single missing tile. I'll try tomorrow on another device.

Why not simply make Locus tell us what "unknown problem" actually means?

64GB microsd with vfat? android 4.1.2? i can only speculate... but at least i am not the only one with this bug. The "unknown problem" tiles are re-loaded properly btw when i scroll them completely out of view and then back in.

No shading or other funky map options involved. Just a basic raster map. Why dont you give us meaningful error messages instead of "unknown problem"?! If this had the java exception or a number or whatever in it, you'd probably have fixed the bug in seconds :-).

Anyway... if you prefer to go the "reproducing" way, i have no idea really. Maybe try your biggest RMAP file (mine are all quite big) and load it from externalsd, if that makes a difference. Then zoom around wildly with two-finger-pinching... let go, zoom again, let go, zoom again, all very quickly, maybe before the previous zoom operation is finished. Thats all I can say about it and thats how it always bugs for me.