10-11-2010 08:38 AM
Hmm, it works on 7.1.
Maybe you should downgrade?
Felix
10-11-2010 09:09 AM
Wait...??!!!??...
What???!!!??!
How did you do that?
I gatta try...
10-11-2010 09:12 AM
You are RIGHT!
You CAN do it in LV7.1, but you can't in LV2009SP1
Go figure!!
Which gives me an idea. I will create a custom control. That might work. Otherwise, I may end up doing something crazy like porting it from LV7.1
Nevertheless, I will post as a request in the Ideas Exchange.
Thanks Felix
10-11-2010 10:23 AM
I checked and the same limitation exists in LV8.5.
So I can't say it is a bug, can I?
10-11-2010 02:11 PM
I seem to recall that it only appeared to work in LabVIEW 7.1 and that when you closed and re-opened the VI, the selective formatting went away. I'm pretty sure the Boolean Text isn't able to actually store the multiple sets of font formatting, and never could.
Can someone with 7.1 test this out for me? I don't have it handy.
BTW, as another potential workaround, you could put the formatted text into a picture and then put that on a button as a Decal so it doesn't 't interfere with the button operation.
10-11-2010 02:19 PM
that when you closed and re-opened the VI, the selective formatting went away
Yup, confirmed this behaviour.
Felix
10-11-2010 03:14 PM
I found a second way this works:
Make the control a strict type def. If you then edit the strict type def to show the underline using the Font DropDown-Box, the underline gets propagated. Still after save-close-load, the underscore is gone.
Just for the fun of it, I'm going to shoot my scripting abilities on this issue.
Felix
10-11-2010 03:30 PM
In LV2009 and LV2010 on Mac (not infront of the windows machine currently). I can set the text up in a string control, then copy and paste it into the boolean text.
10-11-2010 04:11 PM
Matt, do you use a selective underscore? Is it restored after-save-close-open?
My own experiments show:
* it is possible to completly underscore the boolean text, then everything works fine
* I can selectively underscore using scripting in 7.1, with the same results as doing it manually.
My first question at this point: is the selective underscore information saved at all (for porting to other versions). I did use a text (not hex) editor to identify changes, but I'm not sure if the changes I saw where timestamp/GUID stuff or underscoring.
I still have another aproach left: get a LV 7.1 exe handle the selective underscoring during runtime via VI server call from newer versions passing the reference. But this approach is so off the normal way you should program, I wouldn't use it for production code.
Felix
10-11-2010 04:32 PM
I can make it on the Mac and open it in windows (even after saving, closing and reopening), but the method I used to make it doesn't work in windows. I attached the file if you want to mess around with it.