Button text selection start end

[bjustice]

X-POST to NI forums.  (No luck there so far.)
https://forums.ni.com/t5/LabVIEW/button-with-different-size-text/m-p/3864798/highlight/false#M1095147

I am hoping to determine if there is a programmatic method to have a button with boolean text with varying font size/color.  This is achievable with a strong control using text selection end/start.  Booleans expose these same properties in the property node... but it doesn't appear to do anything.

Even more interesting is that I can copy/paste text with varying color/size into the boolean text... and it will work.

Thoughts?  Thanks! 

 

bool_text.vi

[Michael Aivaliotis]

Seems like a LabVIEW bug.

[bjustice]

Darn.  Thanks for looking!

[Benoit]

Well I have been one step further... it can apply the color to all, but report an error...

It it definitively a bug.

Benoit

[bjustice]

Benoit,  thanks for looking at this with me.

It looks like the error that you generated there is a result of the "Vertical Arrangement" property not being allowed to be applied to boolean text.  I get the following possible reasons for that error:

 

So, this is good proof that not everything in the "text property palette" is compatible with boolean text.  Which is fine, but the text select end/start should return a similar error in order to indicate the lack of support.

Also, as I said earlier, I can copy/paste text into the boolean text and have it retain properties.  Which means that the property node interface simply doesn't appear to support programmatic interaction.

 

 

[Benoit]

It's what we call a bug. You should report it.

Benoit

[paul_cardinale]

There's a similar (and probably related) bug when setting boolean text attributes manually:  If you select a portion of the boolean text, then use the Font menu to change something (e.g. the color), it will change all of the text, not just the selected part.  This bug showed up sometime around LV2008; it was fixed in one of the later versions; then it was un-fixed, and we still have it today.  You can get around it by making floating text and setting it the way you want, then cut-and-paste into the boolean text.  (I haven't tried programmatic cut-and-paste; maybe that would work.)

[bjustice]

Interesting history.  Thanks for the information.

I've reported this to NI.  I will post here if they generate a CAR

thanks everyone

[bjustice]

CAR created:

Reference ID 726196.