TL;DR This is a problem for me and other devs (I assume), because:
- Sometimes we have long text/newlines to add help/context/crucial info to settings titles
- These long settings title look terrible in iOS, due to newlines not being rendered
- Crucial information is lost to Android users, due to long lines being cut off
It's no wonder some devs encourage users to use only Garmin Express to modify settings.
As mentioned before, line breaks in settings titles are:
- Rendered in Garmin Express and the simulator settings editor
- Not rendered in iOS
- And obviously not Android, since GC Android can't even show long lines
As mentioned before, this is an issue because some devs put help/notes/explanatory text in the settings titles, since there is currently literally no other way to do so. (Sorry, but the help URL doesn't really cut it, and I don't even think the placeholder text is rendered on all platforms.)
The newlines thing is also an issue because it makes your help text visually pleasing (going back to UX and making a good impression on users, for both Garmin and devs). I've tried workarounds like putting in non breaking unicode spaces or unicode box drawing characters, but:
- They won't look consistent across devices
- They won't work in Android anyway
- They'll make the settings page scroll horizontally on some devices
- There's no way to know what it'll look like on a real device unless you try it
Apologies to fbbbrown, but I will use his app as an example, only because it's my favourite app, it's very popular (100k+ downloads) and I think it's very useful.
https://apps.garmin.com/en-GB/apps/9...7-f92ca02118ad
Dozen Run has a settings title that looks like this:
Garmin Express (looks great):
Enter Zero (0) for Average Pace
or Race Distance (in meters) for Prediction Time.
Rotates Average Pace/Prediction (Time 6 Seconds)
0 = Average Pace field (default);
5k = 5000m
10k = 10000m
...
Marathon = 42195m
...
Advanced add 1%-2% more distance to correct for GPS error.
iOS (almost unreadable)
Enter Zero (0) for Average Pace or Race Distance (in meters) for Prediction Time. Rotates Average Pace/Prediction (Time 6 Seconds) 0 = Average Pace field (default); 5k = 5000m 10k = 10000m
...
Android (I assume):
Enter Zero (0) for Average Pace or Race Distance (in meteSo that setting is probably unusable on Android, since crucial info is missing.
I know this must be extremely annoying as I've asked before, but sometimes it's impossible for me to know if these enhancement requests are even noticed:
- Please render settings identically across platforms, especially long lines and newlines
- Please give us a preview of what settings will actually look like
- Please allow us to add help text (paragraphs) inline with the settings so we don't have to do hacks like this in the first place
Again, not to sound annoying, but I literally cannot understand why it seems like nobody has mentioned/asked for this before, since it's an obvious problem.
