Messages

Hi there
I'm new to beta testing. I have Pro and now installed 3.27.1.2 Free. Now I'm confused, because the Beta Version finds some data from the Pro Version, like my database, icons, etc. - but not my settings. They were obviously all the defaults.
Are they stored somewhere else? I'm sure that would make sense, as a new version might have settings that could confuse an old version. Is there anything else I should avoid in order not to destroy my Pro installation?
Sorry if that has been asked before, but didn't find anything with the search and also on knowledge base.

New Version as of today: rename exising track still impossible.

Weird, for me it's ok now...

Serious bug in 3.27: Cannot save track descriptions
http://help.locusmap.eu/topic/cannot-save-track-description

I'd like to ask you guys to have a look here:
http://help.locusmap.eu/topic/track-editor-move-points-without-changing-timestamp
I think it's more a bug than a feature that moving points with the "Insert/edit" function in the track editor changes there timestamp (even though most of the time it's not significant). At least it's just not intuitive.
Thx!

Route planner, elevation profile:
Some graph hiccup, seems to be going back, which makes no sense on a distance x axis.

Hi Menion!
Didn't see a specific mention of this in the release notes or here, but seems to be fixed in 3.26.2 - thx a lot!

[@slarti76]

@slarti76:
thanks, this screen also needs and improvements. At least quick change in bottom control to unite system little bit. Pinch zoom will be more complicated, and really better title needs an translation, so both later.

Thx, looks much better. I could nitpick that the "OK" button is a little higher on the map selection than on the image selection
Crash is also gone, good!
Can live without pinch zoom, of course. Just a little confusing for user that it doesn't work here but everywhere else...

Crash report 3.26.1:
Tried to add an external app to side panel ("Add link to app"). When choosing the app, Locus crashes. After restart, icon is shown in the panel and app can be started, but "Modify panel" crashes Locus. Modify panel also crashes Locus when called from the presets screen.
Can you reproduce or do you need some kind of logs?

Route planner, elevation profile:
Some graph hiccup, seems to be going back, which makes no sense on a distance x axis.

This is probably not related to the new version, but I noticed something about the "Image Map Calibration" feature: The dialogs to select a point vary significantly from "Select on image" to "Select on map":
Select on Image has OK and Zoom buttons (horizontally) to the lower right, but no two-finger zoom is possible.
Select on map otoh has the OK button to the lower left, and Zoom plus "Center to GPS" to the right, but vertically. And two-finger zoom is possible.
Apart from the "Center to GPS" button, which only makes sense on the map, I think the rest should be identical.
Furthermore, I got an FC: Add a new point, but immediately close the selection screen (on image). Then instead tap the map icon to select on map - boom!
And, last thing: Both selection screen have the title "Select on map" - probably, it would be better to call the first one "Select on image".

Wow! Congratulations, Menion!
Probably the single most amazing new feature since I started with Locus! The editor is so clean and intuitive - great.
And thx to everyone here discussing the development progress - it really paid off!

I think they should be kept, but there's definitely space for a lighter blue, like #7777FF would be nice. And while we're at it, a dark gray like #777777 wouldn't hurt either, as would a real dark green like #005500.
Menion, I know that these colors have a very systematic origin (you sent me the PDF), but looking at them in practice, I feel there's some missing that are more likely to be used in "real life".

PS: Being able to define personal custom colors would be the best, of course. Could be displayed as third section after "ZX Spectrum" and "Secondary Colors".

@menion can one of the blue colors be made more different? a waste of space at present as they look very similar:

I think they should be kept, but there's definitely space for a lighter blue, like #7777FF would be nice. And while we're at it, a dark gray like #777777 wouldn't hurt either, as would a real dark green like #005500.
Menion, I know that these colors have a very systematic origin (you sent me the PDF), but looking at them in practice, I feel there's some missing that are more likely to be used in "real life".

@balloni55: complicated task ... what about people (I believe most of users), who does not use "Presets"?

I'd strongly advise against removing customization options just because they're also doubled in the presets feature. As Menion says, many users, especially beginners, won't use presets, so they'll be put off if they don't find an intuitive way to change the buttons or other settings.
Granted, as is obvious even among us power users, the presets feature is easily mistaken for a "profile" feature and therefore misunderstood. However, it is what it is now and should stay like this - once you understand it, it can be extremely useful. But those who don't use it shouldn't "lose" anything!

@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...

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.

I can confirm this, changing the DPI led to problems with the cursor for ages (ever?). I think I once talked to Menion about it, but I totally understands that this is such an esoteric problem, that he doesn't do anything about it. Have stopped changing the DPI for Locus due to that.

That being said, it's an actual problem that buttons that have reasonable size for "normal" usage are far too small when biking.
@Menion: Did you ever think about this?