LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why did the front panel labels changed to Chinese after building executable in LabVIEW 10?

I am using LabVIEW 10 under Windows 7.

I built an executable of my code and now the English text changed to Chinese on the front panel labels.

Why would this happen and how do I prevent this from happening?

Scientia est potentia!
0 Kudos
Message 1 of 10
(4,323 Views)

Magyar,

 

That is strange! Some questions for you.

 

1.) Does this happen for all VIs that you try to build into executables? or just that particular VI?

2.) LabVIEW 32 or 64 bit? Windows 32 or 64 bit?

3.) Is the OS an English edition?

4.) In the Executable Build properties, check the Run-Time Language category. What is set for the default Language? What about the Supported Languages?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ben Sisney
FlexRIO V&V Engineer
National Instruments
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
0 Kudos
Message 2 of 10
(4,289 Views)

1.) Does this happen for all VIs that you try to build into executables? or just that particular VI?

A: No, the second time I had english but enlarged characters. The enlarged character got smaller(just a little different from the source code) when i set the display setting to 100% instead of the previous 125%

 

2.) LabVIEW 32 or 64 bit? Windows 32 or 64 bit?

A: Windows 7, 64bit, Labview 2010,32bit

 

3.) Is the OS an English edition?

A: English

 

4.) In the Executable Build properties, check the Run-Time Language category. What is set for the default Language? What about the Supported Languages?

A: I checked English only

 

Anyway, it did not happen again. I might also mention that yesterday Labview quit on me, without warning, simply all labview related windows disappeared while I was manipulating the block diagram og a complicated VI. The two might have something common,

mAYBE A MEMORY CELL WAS HIT BY gALACTIC cOSMIC RADIARION? 🙂

 

Scientia est potentia!
0 Kudos
Message 3 of 10
(4,274 Views)

tHIS IS MY SYSTEM INFO

Scientia est potentia!
0 Kudos
Message 4 of 10
(4,273 Views)

Magyar,

 

Glad to hear the issue went away. I couldn't find any Bug Reports of this happening. If you are able to find a set of circumstances that are reproducable, please post them back on this forum so I can file a bug report on it. Thanks for the system info!

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ben Sisney
FlexRIO V&V Engineer
National Instruments
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
0 Kudos
Message 5 of 10
(4,252 Views)

Hi,

 

Just FYI, I've also had a similar problem with LabView 8.6 in Windows XP on an Intel CoreDuo system.  All LabView windows simply close down in the middle of a run, or in the middle of an edit.  No warning, and even the intro. menu when first starting LabView was gone.

 

No idea what is causing it.

 

Mike Hinckley

LM Coherent Technologies

0 Kudos
Message 6 of 10
(4,171 Views)

Hello

I have had the same experience as mkh, using Labview 2090 with XP on a Dell with Intel Pentium 4 CPU.

 

The particular events occured to me when using an ActiveX container and trying to drop a QT object into it.

 

Everything just disappeared, even the getting Started spalsh. Tried it again and it worked...tried it again and it disappeared.

 

Ray

0 Kudos
Message 7 of 10
(4,165 Views)

Sounds like a possible bug with 8.6 and later.

 

Ben, thoughts?

 

 

Mike H.

0 Kudos
Message 8 of 10
(4,150 Views)

I'm fairly certain that the LabVIEW crash has nothing to do with the strange executable behavior discussed on this post. When LabVIEW closes without warning it is either a crash or LabVIEW closing to prevent corruption of files. When you restart LabVIEW after one of these instances you should get a window that says somthing like, "The last time you ran LabVIEW an internal error or crash occured," and it will list a .cpp file where the crash occured. You can use the LabVIEW Internal Errors (Failure in XXX.c / XXX.cpp at line YYY) document to troubleshoot some of the more common causes of the crashs/closes. If you select the option to investigate the crash now, it will generate a crash report service request that will get sent to our Applications Engineering Department.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ben Sisney
FlexRIO V&V Engineer
National Instruments
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
0 Kudos
Message 9 of 10
(4,133 Views)