Android Question All views that display Text should auto-adjust font size?

JohnCody said:

Am I missing something?

Click to expand...

The easiest way to answer this question is: give it a go. In fact, you can do it right now in many instances by using a text size of "-2".

https://www.b4x.com/android/forum/t...pending-on-a-views-content.75533/#post-479335

The main problem is that you end up with something that looks like an early-desktop-publishing-era font explosion, where every text on the screen is a different (but perfectly-fitted ;-) size, usually with a grotesque outlier or two. Or if you set the font size and vary the container to suit, then you end up with eg: "randomly" sized buttons, and with the most-commonly-used "Ok" button being smaller than the "Cancel" button, which is usually the opposite of what you want from a usability perspective.

And then of course you have the annoying zooming-in-and-out out-of-focus sensation of text that varies, eg, if you are displaying names from a database, and you move from Jon's record to Jonathan's record.

I can't think of even one situation where it would be OK to display cut-off text to the user.

Click to expand...

We've been cutting off text for display since the year dot, yet survived OK. We call it scrolling. But I can understand this example wouldn't have immediately sprung to mind, given its ubiquity.

Righto, having said all that: you can get pretty close, though. I've never been able to get the AutoScale+Anchors to do precisely what I need, and I'm too lazy to use the non-visual designer scripts, so I wrote a routine that I thought would solve all my problems, and it works pretty well, except... every new use of it seems to require a new special option to handle some new not-quite-right rendering. One thing that helped was applying the fits to groups of objects, eg, saying that "all these buttons should use the same size text" rather than fitting to each button individually and having different size text in each button.

Anyway, try the -2 trick, that's an easy way to dip your toe into the game.

It looks like that -2 trick will resize the view's height or width size to accommodate the text, and not change the font size. If so, then depending on all the different text strings and the device's screen specs, you could surely end up with a mess of different view sizes then what the developer intended the layout to look like.

But, I'm thinking a better approach might be to let a view adjust its size automatically as it does now using the anchors. But then consider the font size that the programmer initially set for a particular view to be that views' "max" font size. Then ONLY allow the view to make the font size "smaller" if the text wont fit within it. This would hopefully at worse minimize the number of different font sizes on an activity, and at best actually have no different font sizes from what the developer initially designed the app with if no changes are needed.

My thought is that a user would rather see some text in a smaller size, then get text cut off.

JohnCody said:

It looks like that -2 trick will resize the view, not necessarily the font size.

Click to expand...

Hmm, you could be right. I was sure that the -2 was a trick you could use for TextSize too, but now I can't find the forum post.

I did find this during the search, though:

https://www.b4x.com/android/forum/t...adding-in-a-loop-for-all-views.43284/#content

so it looks like I've been doing some wheel reinventing myself anyway. Spewin!

My thought is that a user would rather see some text in a smaller size, then get text cut off.

Click to expand...

Except for the outlier cases, where the text becomes smaller to the point of being unreadable. Sometimes truncation is the better option, although it helps to have some indication that it's been done, eg, the ellipsize option of Labels et al.

I saw an address once, to "Gembrook Launching Place Road", which seemed to have been shortened by removing presumed-redundant text "lace Ro" and thus became "Gembrook Launching Pad" which was funny because Gembrook is a idyllic small town with a daily steam train service, and the last place you'd expect to be launching rockets.