Improved Text Elements
I frequently use text area elements to clean up my UX's by concatenating/consolidating data from preceding elements. While text wrapping is automatic, height is fixed.
I can specify the number of lines showed on the device using \t, \n etc.
That won't be an issue. If I'm setting the default height of the object, consider it an output. I use Tab, Line Feed and Line Breaks to assure that the information populating the element is consistent across all devices. Consequently, there would never be a risk of less or more lines showing than I want to display because presumably I'd catch that during development or testing.
It has to be this way in my case because showing the text element provides narrative and data from other preceding elements in a summary format intended to allow hiding of previous elements and a less cluttered interface.
The risk you mention above pertains more to user input, the "traditional" use of the text area element, and actually that's another limitation that might be worth addressing. That case arises where I do NOT want to specify a default height because I'm using the text area in the normal fashion, a place for the user to enter comments. An enhancement might be allowing height of the element to expand or collapse automatically based on the amount of text entered by the user. If the user enters two lines, the text element is two lines high, four lines, four lines high. You're already wrapping the text automatically, so having the element become fully dynamic in this manner would be very desirable at least in my case.
I think you and I are actually on the same page. I was teasing out your requirements because something that's been proposed is a property for read-only elements to change their appearance from a text element that has been filled out to text directly on the background of the app without the white backdrop. The original intention is to retire the read-only attribute on text elements but it may be able to accommodate your multi-line read-only reference use case!
What do you think? If you're not sure what I'm talking about then try to turn on the read-only attribute (checkbox) for a text element.
Please sign in to leave a comment.