Most of my string controls are only one line high and accept maybe a single word or small string that should remain a single line (table header, file prefix, etc.). For these controls, it is much more intuitive to be able to end the entry with a <enter> key, but if they are not set to limit to single line (The default for strings! 😞 ) pressing the enter will just add a linefeed, making part of the string disappear from view and polluting the string with a newline character that should not be there.
I am proposing a VI analyzer test that would find all string controls that are relatively shallow, but have the "limit to single line" not checked and/or still have wrapping enabled. These options only make sense if the string control has room for several lines.
Should be easy to do, right?