Messages

[@tapio]

@tapio

I think you meant me

PiP display: it is possible that panel ratio affects resize options. Anyway, this panel was made mainly for navigation. For this case it is optimized and because of this, it is a little higher. I do not see a sense to increase its size close to the full-screen.

No, I agreed, fullscreen makes no sense. But look at my screenshot: Imagine this in >50cm distance while biking, that is basically pointless! Perhaps this is something Samsung-y and not like that on your phone. But for me, it's now useless, whereas in the initial beta I could at least get it to ca. double the width, which makes it usable.
Please add an option to choose ratio (e.g. 3:2, 1:1, 2:3 is enough)!

Automatic zoom & rotation works for me as well as no glitches as balloni55 wrote above. Sorry, there is not much I may do for now.

Ok, will check automatic zoom again, didn't get around to check it with release version. Rotation works, I can confirm.

[@slarti76]

Menion, you still looking at this? I checked again with release 4.9.0, but behaviour was the same, apart from map rotation now working.

@slarti76
Locus & Pokémon GO 

Guilty pleasure...

Thanks for the tests! You were really able to resize and move this PiP window fully freely? Weird, it should not be possible.

Well, as I said, ratio was fixed, but I could make it much bigger. Is that really not supposed to be possible? I mean, e.g. if I use VLC as pop-up, I can resize it to like 90% of the screen width (but also the ratio is fixed).
Ah, I just realized something: A video is, of course, in landscape - so resizing to full width is possible. Locus was initially 1:1, which obviously also allowed it. Once you changed the ratio to 3:2, it's not possible anymore, because then you could basically resize it the more or less full screen size. So Android doesn't allow it. Of course it's ridiculous why Android forces this on the user, also that snapping to left or right of screen, but we all know Google...
Does that sound like a possible explanation to you? (I don't have a portrait video around that I could try with VLC...)
Anyway, perhaps you could at least let the user choose whether it wants the pop-up in portrait, landscape, or square. Everything after that is Android, and we have to live with it. But 3:2 portrait is very likely not what you want in every situation...

It is also not possible to define own custom buttons there. For this, you may simply use the split-screen mode of your device, you do not need a PiP.

Sure, ok. But then why have that bar at all? As I said, just put the Navi Icon in the upper left and voilà - space saved...

- map zoom > there should be no changes when switching to PiP, so you should see a zoom visible on current map.

Oh, you're right, didn't realize that. However, I had "Automatic Zooming" on, and that doesn't seem to work in PIP - could that be enabled there, too?

Oh, and additional thing: Does anyone else notice that the Text-to-Speech setting is reset? I always set it to none (don't want any audio output), but it happened to me at least three times now that after an update, it was active again. And once, I even suddenly had miles instead of km as distance unit.
Nothing severe, just a little worrying that settings change out of the blue, wondering if others experienced that, too...

[@slarti76]

@slarti76
Locus & Pokémon GO 

Guilty pleasure...

Thanks for the tests! You were really able to resize and move this PiP window fully freely? Weird, it should not be possible.

Well, as I said, ratio was fixed, but I could make it much bigger. Is that really not supposed to be possible? I mean, e.g. if I use VLC as pop-up, I can resize it to like 90% of the screen width (but also the ratio is fixed).
Ah, I just realized something: A video is, of course, in landscape - so resizing to full width is possible. Locus was initially 1:1, which obviously also allowed it. Once you changed the ratio to 3:2, it's not possible anymore, because then you could basically resize it the more or less full screen size. So Android doesn't allow it. Of course it's ridiculous why Android forces this on the user, also that snapping to left or right of screen, but we all know Google...
Does that sound like a possible explanation to you? (I don't have a portrait video around that I could try with VLC...)
Anyway, perhaps you could at least let the user choose whether it wants the pop-up in portrait, landscape, or square. Everything after that is Android, and we have to live with it. But 3:2 portrait is very likely not what you want in every situation...

It is also not possible to define own custom buttons there. For this, you may simply use the split-screen mode of your device, you do not need a PiP.

Sure, ok. But then why have that bar at all? As I said, just put the Navi Icon in the upper left and voilà - space saved...

Anyway
- map rotation > agree, I'll look at it.

Thx

- map zoom > there should be no changes when switching to PiP, so you should see a zoom visible on current map.

Oh, you're right, didn't realize that. However, I had "Automatic Zooming" on, and that doesn't seem to work in PIP - could that be enabled there, too?

Oh, I also tried the improved map shading. My result is very surprising: While the slope shading is greatly improved (screenshots 1&2), the Hill Shading shows no improvement at all (screenschots 3&4).
All screenshots are ZL12 with 2xEnlargement and ZL13.

Some thoughts about PIP:
First of all, I like it very much - finally playing Pokémon GO on the bike and navigating with Locus at the same time (don't tell the police .
I tried it today, but still had 4.8.2.1 - before I write a post, I thought I'd update... But something's broken in .2: I can't increase the size of the window to more than half the width of my screen. Before, I could increase it to like 90% of full width. Like this, it's much too small. It's also 3:2 now, instead of 1:1, but it's always fixed, which I find an unnecessary restriction. Depending on app that is overlayed I'd prefer to be able to change size more or less freely.
I'm also not able anymore to move it anywhere - the window is either magnetic on the left or right, I can't have it in the middle.
All that worked before (apart from the ratio which was always fixed).
Some more observations:

• The bottom bar only contains the navigation icon and distance - wasted space. Are you planning to add buttons here? Because otherwise, I think it would be better to just overlay the navigation icon in the upper left corner, just like in fullscreen
• The map is always north-up, even if I have map rotation on in fullscreen. For navigation, map rotation is a must.
• The zoom is very close. I can perhaps see 100m in all directions. Is that on purpose?

PS: I never had a problem when switching between PIP and Fullscreen, Locus never disappeared or the like.

[@luce]

@luce
I agree with michaelbechtold. Maybe not so nice, but definitely a little more detailed. Anyway as you may see on your screenshots, there are some graphical glitches that I was not yet able to solve. Hope that current style is not a problem.

I also agree that the detail is more important (hey, I was the one asking for it ). But when I compare the screenshots, the new one also looks less saturated. Perhaps a little tweaking of the alpha value for the shading would make the effect more pronounced and thus better looking?

Hi Menion
I know, I've been coming up with this several times before, but I'm trying it again - perhaps now that Locus 4 is running more and more smoothly, you find the time:
It's about the MapShading: I'm still unhappy that the resolution of the shading is artificially lowered between ZL12 and 13. I posted screenshots before, could do it again, but it's easy to see for everyone. The difference is so stark that setting the Magnify Factor to 200% in ZL12 still produces better shading than ZL13.
One might argue that it's partly astethic, but at least for the Slope Shading, it is not: For snow tours in the mountains, the 30° slope level is the most important factor for avalanche risk assessment, and losing obviously possible resolution here is just a shame.
I know, speed can be a problem here, but for most modern phones it isn't, so it's just wrong to force the resolution-decrease for a specific ZL for everyone.
I think it would make a nice "Expert Setting" to be able to increase the ZL or turn this "Optimization" off completely.
What do you (or anyone else) think?

[@slarti76]

@slarti76
sharing a photo, hmm, I'll look at it ...

I see it's implemented in 4.6.1.5 - much appreciated, thx!

After years, I used the geotagged-photos-on-map feature again. I noticed that the share button only shares the position. Even if I click on the picture, it open in a window, but there's no way to open it in another app, like my normal gallery. I think there should be a share button, at least in the picture view, better directly on the icon. Currently, long press on the icon opens a "menu" containing only "Set as icon" as option. This would be a perfect place to add (system) share without much effort.

Got two small observations:

• The new "minimized point/track pull-up" is nice, but I would prefer if that flag is "sticky". Let's say I have several tracks close to each other and click one, then click the pull-up title to make it small, to just see the name. Now I click another track, but I get the big pull-up again. It would be nicer if the pull-up stayed minimized while clicking through points and tracks. Once I unselect everything, the flag is cleared, so next time I click something I get the full size again. In short: "When track/point clicked && already a pull-up shown && pull-up minimized => show new pull-up minimized"
• I never before saw this "Show View" function. It's nice, but - at least on HD screens - basically useless, because it's so small. On my screen the >50% transparency part is ca. 3x3mm, and when I'm e.g. on a motorway, which is usually yellow or orange, it's almost invisible. Could you add a %-size selection in settings? Btw, when I long-click the button in Quick Settings and chose "Information", an empty message is displayed.

Android is really weird since A11.
"Android/media"

App create directory with the package name, so /Android/media/menion.android/locus/x
- app may read and write here without limits
- directory is deleted together with the app!!

So the main difference to the folder in data is that at least file manager apps have full access here, whereas in data they only have on the intSd (which may or may not actually be a bug that Google decided not to fix in A11 in order not to break something).

App may also create any! directory here, so for example /Android/media/maps
- app can not read any content from this directory. Simply request "get files" return "nothing" even I've just put few maps there.
- directory is not deleted together with the app

Well, that really makes no sense, granted. Being able to create directories you can't read from - oo-whee!

Then we're back to the question whether generic folders like Android/media/maps would work, i.e. Locus can access them the way it needs, and they're not removed by any deinstallation (which I'm pretty optimistic about, there's no way for Android, at least on ExFAT, to be sure which app created a folder, if it doesn't conform to a specific naming scheme).

Without harm means that the app is not important to me.

Ah, OK, thx, now I understand.

I just checked /Android/media and found an app that puts a folder there and that I could dispose of without harm: the app specific folder in media will go with the deinstallation.

I'm sorry, but you're also contradicting yourself: Can you dispose of the app without harm (= without the folder being deleted) or will the folder in media go (=be removed) with the deinstallation.

Anyway, because I create app directories manually, there is a change, this dir won't be deleted ... what a stupid Google decision, omg.

This contradicts what I answered me above - so did you try it out or otherwise came to the conclusion that the folder under media is not deleted?
I'm totally confused now.

As an aside:
I do understand and kinda support that Google doesn't allow everyone to write directly to the root folder of intSd or extSd (incl. not creating directories) - that only led to chaos with tons of folders like "backup", "Backup", "backups", "bak", "tmp", "temp", "tempAppName", etc. Their "solution" approach, however, goes much too far, obviously, and is too restrictive.