Hi Eddie,
Good answers, I think we can try to track this thing down. I installed LabVIEW 6.1 on a solaris 2.9 machine today and didn't see this problem. What I was doing is opening up a blank VI and placing a string control, and then typing values in the string control. I couldn't get anything to do what you are seeing.
I was brainstorming why the XP webterm and the linux x server might be different. This is what I think:
1. Environment Variables. Sometimes certain programs like SSH, telnet, rexec, etc will carry over certain environment variable for you. They will also cause different login scripts to be executing. Maybe in one of the scripts or environment variables something is being done to remap the keyboard, use different
fonts / etc.
2. Fonts. Maybe there is a font being used that doesn't have a displayable character for those three characters? (that's weird if so), try changing the font with the font selector
Here are some more tests that will help narrow down if this is an input problem, or a font problem:
1. Do "File -> Open", can you type "r" in the filename path?
2. In a string control, type "r", then right click on it and change it to a hex display, do you see "72"?
3. In a string control that is set to hex display, type "72" and then change the control to a "normal" display, do you see "r"?
4. Use a password display string control, type "r" and see if you get "*"s in place of the "r's"
5. Create a program with an event structure that watches for "this application -> key down" (in a while loop). Right click on the "char" data node and do "create indicator". Run the VI, you should see the numeric update each time you press keys, "r" is 114.
I know these tests might be time cons
uming, but I tried them all here on my solaris machine. Let me know how these tests work out for you and any other tests you might have came up with.
Thanks!