Some indication that a string control isn't showing the entire string.

[Lavezza]

I'd like there to be an option to show some kind of indicator on string controls that you aren't seeing the entire string. This should also apply to string constants on the block diagram.

I searched for a similar idea, but couldn't find one. Let me know if there is already a similar idea.

[Darren]

I like the pink better...it's more subtle.  But either way, this idea rocks.  Note that we currently have a VI Analyzer Toolkit test that will detect these situations (Front Panel > User Interface > Clipped Text), but edit-time notification like this is even better.  Kudos for you!

[Lavezza]

Darren,

I'm pushing to get VI Analyzer. Do you know if it finds clipped text on block diagram constants?

[Darren]

The Clipped Text test for the VI Analyzer Toolkit only analyzes front panel objects.

[Vaibhav]

I must say I liked the pink color because it's calm and gives a change from the boring gray 😉 but I suggested gray just because to be coherent with other things (pink is coherent with string datatype by the way).

Also, yes I also thought about giving a little more contrast but you know, then the special indicator will be very close to the default color of the indicator. But yea, it can be made a little lighter than now. 

And about "...": in fact, that came to me as the first thing in mind before the >> type sign, but again, that "..." can merge with the existing text (so you cannot actually say if it's that "missing text" indicator or not), and if you use some special background color to notify that "..." is for indication of missing text, then it will occupy more "space" than the narrow >> or << would do. But yes, the three dots is the first and intuitive thing that comes to mind while talking about missing text (or continued text).

Thanks for everyone for appreciating the efforts, and Kudos to Lavezza for reading our thoughts 😉 (I think Lavezza's status rank changed recently ;)).

[Tom_Hawkins]

The standard way of showing that a longer piece of text has been truncated is the ellipsis (three dots, ... ). Much better to use that than introduce yet another piece of visual language unique to LabVIEW.

To make it clear that the ellipsis isn't part of the text, it could be shown in a lighter shade, i.e. grey for black text.

In Aristos's example I would show the ellipsis in the bottom right corner of the multi-line text box.

There could also be the option to show the ellipsis in the middle of the text, rather than at either end. This is useful in cases where the significant information is at the end of the text ("An error occurred while reading from DeviceWi..." is rather less useful than "An error occurred w...iceWithUnexpectedlyLongName5", for example).

[Manzolli]

Three dots as a special character: Unicode Character 'HORIZONTAL ELLIPSIS' (U+2026)

[Swimmer]

It's not just for strings.

How about all controls & indicators that display strings or values.   

[X.]

Agreed DVS! I posted an idea  in this direction.

[G-Money]

Thanks for posting the new idea showing how the tip strip could be implemented X.! Everyone should check out the other idea and comment on if you would like the tip strip to be an option for this higher level ellipsis idea but make sure and bring your kudos back to this idea as it will be the one driving this feature request.

[altenbach]

> Agreed DVS! I posted an idea  in this direction.

I fully agree that it should apply to numerics (and others) not just strings.

We've seen cases in the past where the poster thought the result was quite different that what was implied by the numeric indicator due to truncation. (e.g. 1.2345E-18 or 1.23456E+54 might appear as 1.23456, orders of magnitude off! 😞 )