Issue with Custom Menu Bar in LabVIEW Application on Chinese OS

[JW_KSR_9850]

I am facing an issue with an application build created in LabVIEW.

My main.vi uses a custom menu bar, which is included in the Always Included source files of the build specification. I tested the application on a Windows 11 system and on another Windows 10 system, and the custom menu is displayed correctly on both.

However, when running the same application on a PC with a Chinese version of Windows, the application shows the default LabVIEW menu bar instead of the custom one.

Has anyone encountered a similar issue or has an idea what might cause this behavior?

[Kyle97330]

I've not encountered this exact problem so this is just speculation?

Can I assume by "application build" you mean a compiled EXE?

If so, what options do you have set for languages in the build settings?

I am wondering if maybe having Chinese supported, as it is by default, could actually be part of the problem somehow.  Perhaps part of the "support" for it is overriding the menus, so if you remove it then it will stop trying to "help" and the actual menu you specify will be used instead?

The only other thing I can think of is to look into using the menu palette instead of a custom menu bar.  I'm sure it would be annoying to have to dynamically create the menu for each VI in code instead of just making a menu file you attach, but it could be that forcing it to make a menu at run time (as opposed to load time for the custom menu bar) could override the undesired behavior.

[JW_KSR_9850 · Accepted solution]

Thank you very much for the quick response.

I believe I was able to resolve the issue.

I wanted to modify the Runtime-Languages settings and noticed that I do not have this tab at all. According to the LabVIEW documentation , these settings are only available for 32-bit applications, whereas I am using 64-bit.

In this case, the application uses the locale selected on the PC, which was set to English.

I changed the PC locale to Chinese and built a new EXE. It now seems to be working correctly.