Multilanguage user interface

[PinguX]

Weird, I checked and it works great on my computer.

Is it possible to send your VI ? (saved for previous version of LabVIEW, 2019/2020)

[paul_a_cardinale]

---

@PincoG wrote:

Hi PinguX,

I already turned on both of them, and also turned on Interpret as Unicode just before setting the txt.

Nothing happens in developping.

---

"Interpret as Unicode" is applied character-by-character, like a font style or color.  Which characters are affected depends on the setting of the text selection.  

If you empty the string, then set "Interpret as Unicode" to TRUE, then future text stored will be interpreted as Unicode.  Note however that when you type text into a string, LabVIEW tries to figure out whether it's ASCII or Unicode (unless "Force Unicode Text" is set to TRUE, in which case it assumes that everything coming from the keyboard is Unicode).

[PincoG]

Hi Paul,

my problem is not with the contents of string control.

Is a problem specifically with boolean text.

as you can see in this reduction example, Caption works pretty well, boolean text property not.

I don't know why.

[PincoG]

Version 2019

[PincoG]

I noted something: 

if I start from a "clean" button, the first text seems ok (only the first I mean).

So I do not find any hope to make multiple strings to work well in 2021.

does anybody know if it works better in 2025?

Does anybody know if there is any improvement in new versions/Help system ? 

I mean properties Description and Tip Strip ?

[PinguX]

To start from a clean button, it is possible to reset the boolean strings displayed, by setting an empty array of string to "Strings[4]" property.

See attached.

By doing so, it is also possible to switch between Unicode and non-Unicode strings.

[paul_a_cardinale]

---

@PincoG wrote:

Hi Paul,

my problem is not with the contents of string control.

Is a problem specifically with boolean text.

as you can see in this reduction example, Caption works pretty well, boolean text property not.

I don't know why.

---

There is a bug in "vi.lib/addons/Tools/Unicode/_subVIs/Display Boolean.vi"

Do something like this instead:

Alternatively, I have attached a repaired version of "Display Boolean.vi".

[paul_a_cardinale]

---

@PinguX wrote:

To start from a clean button, it is possible to reset the boolean strings displayed, by setting an empty array of string to "Strings[4]" property.

See attached.

By doing so, it is also possible to switch between Unicode and non-Unicode strings.

---

That doesn't always work.  To work all the time, send an array of empty strings to "Strings[4]" (not an empty array).