02-15-2010 12:22 PM
hi
the link you provided gave an Erorr. please check it
(Error
You are not authorized to view this document)
@for the bilingual joke : it is not japanese, it is chinese... 🙂 and I am already multilingual... but what can I do with the squares .. see http://forums.ni.com/ni/board/message?board.id=170&thread.id=471918&view=by_date_ascending&page=2
02-16-2010 03:26 PM
Hi guys,
Sorry, can you please post the VIs that are causing the problem?
02-16-2010 06:07 PM
Here it is.
02-16-2010 11:17 PM
Smootastic wrote:Hi guys,
Sorry, can you please post the VIs that are causing the problem?
please see here : http://forums.ni.com/ni/board/message?board.id=170&thread.id=471918&view=by_date_ascending&page=2
02-18-2010 03:09 PM
Hi dycor,
Try changing some of the controls on your front panel to constants and then reverting them back. I tried this on your VI and it seemed to fix the issue.
Unfortunately, this issue has been reported in Corrective Action Request (179683) and is currently under investigation by R&D. For now, a potential workaround is to convert the controls/indicators to constants and revert them back. Additionally, this appears to be an issue when using a VI that has been built into an executable.
I'm sorry for the inconvenience.
02-18-2010 03:35 PM
Since this is my original post I will add what I have found on this issue.
1. Symptoms: after build some system/dialog font strings become corrupt, and appear to be some asian type character set. This is NOT a simple font change and it can be on string constants, lables, boolean text ....
2. Very rare but has happened to me.
3. If vi are not saves the font reverts to the unsaved text.
4. Ni did provide me a tool that used private property nodes to correct the corrupted vis, it has something to do with unicode?? I never tested this vi since I immediatly rolled back to a ghosted (previous version) of the code and distroyed the vi, I didsend the vi to NI and this was used for developing the tool.
5. After each built the vi became corrupted again. Once I deleted my .ini file (labview one) the problem went away, it was not a corrupted labview copy but something to do with settings???
6. This will happen at the least opportune time (SEE MURPHY)
This is all I can provide on the issue.