From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
03-01-2021 06:42 PM
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?
03-01-2021 11:02 PM
03-01-2021 11:48 PM
Posting by phone, will look at it later. Looks promising. (Not sure why my earlier search could not find this...)