Settings UI demessification: add "Display" page, remove "Global" page.

joeloc shared this idea 3 years ago
Completed

Locus settings get messier by the minute. Here`s a quick little idea to get rid of that silly "Global" page. It is a pointlessly confusing title... as if all other settings were not global?!


Anyway... almost all the stuff in "Global" is about the display, so why not just call it "Display"? As for the remaining items:


"Confirm on exiting": This is useless as a prefs item, delete it! The option should instead be added directly to the exit confirmation dialog as a checkmark ("o dont ask this question again"). Same applies to all other confirmation dialogs! The one and only option you are allowed would be "Misc / Show all dialogs" to reset the state of all those flags at once.


"Locus as a service": Move that to "Miscellanous". It is unusual enough to not show up that prominently.


"Language:" Move that to "Localization".


"Text to speech": Move that to "Localization".


Thats it: Silly "Global" page is dead.

Comments (11)

photo
0

On a related note: almost every single one(!) of the English settings item texts has bogus grammar and/or wrong spelling and/or wrong punctuation (or is in fact incomprehensible nonsense). Doesn`t a professional app like Locus deserve proper language? It`s not a major usability problem obviously, just ugly and a little bit embarrassing. Wouldn`t it scare away potential buyers?


I wonder if the problems with the super-inflexible translation system are fixed meanwhile. Or are the English strings still basically unchangeable and will remain set in stone forever and a day? That would really be a shame :(.

photo
0

Hi,


I’ll discuss it with Menion when he comes back from holiday. Anyway I have to agree with you with some points...setting is from my point of view very complicated.


* New section display – good point


* Confirm on exit – not sure


* Locus as service in “Miscellanous” – why not


* Language in “Localization” - good point (or rename it on Localization & Units)


* Text to speach - I’d like to have one settings for Guiding and Navigation. We’ve tried to join mentioned section into one but there is lots of different settings that it’s not possible. But TTS settings should be place here (in Guiding or Navigation)

photo
0

TTS in guide and/or navigation sounds reasonable today. However... maybe in future Locus will become a bit more talkative and offer stuff like


o Announce current altitude changes every __50__ m.


o Announce accumulated climbing every __100__m.


o Announce accumulated distance every _1_km.


Those would have nothing to do with navigation or guiding but still require Text To Sync Settings. There are in fact dozens of other places outside navigation where more TTS would be handy.

photo
0

- two settings moved to misc


- two settings moved to localization


- "global" renamed to "display"


I was thinking about removing "Confirm on exiting", but I do not agree


About quality of English - nice, right ;) ... ah just kidding. We know about this. It`s just "my" English. Crowdin has a problem with changing words in default language, but it`s not so big problem now. If you see any really bad sentences and descriptions, I`ll gladly change it ...

photo
0

Menion wrote I was thinking about removing "Confirm on exiting", but I do not agree


what about


"press `back` again to exit"


?

photo
0

hmm I`ve changed "Confirm on exiting" button to this behavior and we`ll see if this is best way to end locus or not

photo
0

no effect in v2.16.0.10 yet...


...nor in v2.16.0.11

photo
0

hmm current there are two ways ...


1) menu > settings > misc > Confirm exit - enabled => standard locus close (yes/no) dialog


2) menu > settings > misc > Confirm exit - disabled => close on twice back press as you suggested. Previously this settings just minimized locus, but it`s quite a nonsense because it was then same as "home" button

photo
0

ahh settings - good hint ;)


i like it !


but the green requester should be closed immediately.


currently it`s still there for a second - after(!) locus has quit.

photo
0

They are almost all bad really... :-), I don`t think it makes sense to fix just one or two. This will not change a new users first impression. It`s not that you cant understand Locus with a little bit of fantasy, but I guess new users might associate buggy language with a buggy program. Oh well... cant be changed with Crowdin I guess. Never mind.

photo
0

About "confirm on exit - off"


Tested this setting now on a very short offroad trip:


Please don`t allow a fast doubletap !!


eg 0.5 second minimum between 1st and 2nd tap


because my bike shakes and my fingers are not really controlled on the road. ;)