11-30-2005 10:30 PM
12-02-2005 10:46 AM
Hi rmp,
I think this document on Porting and Localizing LabVIEW VIs will be helpful. It has a lot of information on fonts and potential problems. The difference could be explained by the change in resolution or by the fact that you're not using the default font size.
Check out the tutorial and please post if you have further questions,
Megan B.
National Instruments
12-02-2005 02:15 PM
12-06-2005 04:36 PM
Hi,
The document that Megan B pointed out mentions that the Application font, the System font, and the Dialog font map best among different platforms. When you port a VI that contains one of these fonts to another platform, LabVIEW ensures the font maps to something similar on that platform.
If you do not use the defined fonts, the font can change size on the new platform because of the differences in the fonts available and differences in the resolution of the display on the other platform. For example, if you select Geneva or New York on the Macintosh and port the VI to UNIX, LabVIEW cannot find that font name on Windows and substitutes it with Arial. The substituted font may not match the original, and objects may overlap. If you port a VI to Windows and Windows does not recognize the fonts, the new font may display differently.
If you use a defined font on a section of text, avoid changing the size of that text. If you change the font to something other than the default size and then port the VI to a different platform, LabVIEW tries to match the font with the new size, which might be inappropriate depending on the resolution of the screen.
Hope this helps,
Ankita
12-06-2005 06:48 PM
12-08-2005 03:50 PM
Hi,
Thanks for clarifying the question.
I created a VI with Arial , Georgia and Time New Roman fonts with rectangles around them. This VI when ported to Mac does so substantial differences in size and boldness. You were absolutely correct.
I talked to a LabVIEW developer about this and we feel that this is something R&D team needs to look at more closely. It is either a bug or something that skipped our notice thus far. Hence I have files a Corrective Action Request for this issue for further investigation. Thanks for your feedback.
As for now, I cannot suggest any other workaround but to try and use system or application fonts and make sure they look similar on both platforms.
Regards,
Ankita
12-08-2005 04:24 PM
12-08-2005 05:51 PM
12-08-2005 06:11 PM
12-08-2005 08:33 PM - edited 12-08-2005 08:33 PM
Stay focused on those issue already mentioned. At the minimum, just one combo to start, but...
if you can look into LV's built on VI functionality when a user selects a larger system font?
It is real easy to tell what part of LV's GUI is developed in LV (PID Toolkit), and what is not. (Sure I can edit and save as a new name, but I loose upgrades that come down the pike.) I suspect your internal stuff like that follows all of the rules but you end up in a situation were you can only read part of the number or files spec.
Admitedly asking for the moon,
Ben
Message Edited by Ben on 12-08-2005 08:34 PM