Jump to content

User defined glyphs in icon editor


Recommended Posts

To create user defined glyphs in the icon editor the Windows documentation states the correct place for the .png files is under the \LabVIEW Data\Glyphs\.

Using 32-bit LabVIEW 2016 with OpenSuse Leap 42.3 the location should IMHO be ~/natinst/LabVIEW Data/Glyphs but this does not seem to work.

I have tested that the glyph files can be loaded from wherever, so the file format is correct, but I would like LabVIEW to load these to the Glyphs menu in Icon editor.

Refresh does not help. I'm thinking the glyph files are probably in incorrect folder.

Has anyone managed to accomplish this, and could you give me a hand with configuring this?

Link to comment

I managed to figure out the solution to this, so will share it here.

In this article there was a mention of the setting, that defines where LabVIEW will look for the icons and glyphs.

In Options/Paths the default value for the "Default Data Directory" path is /root/natinst/LabVIEW Data.

=> this then is the correct place for also the user defined glyphs, and I can verify that this works.

After any change, do delete the Glyphs.<LVversion>.bin file in the same folder. This will force the LV to recreate the glyph cache, no need to restart LabVEW.

Link to comment


This issue arose from the fact that I could not easily figure out a way to fix the glaring font issue in the icon editor, so to go around that I decided to create the letters I use in icons as glyphs instead.

These might come in handy for other users as well so I'm sharing them here.


There are better solutions for this I'm sure, thus this is only a stop gap hack.

Edited by Deep_Blue
Link to comment

Hi LogMAN,

thank you for the reply, it does indeed.

However attempting to fix the issue with the instructions on that page offered no help for me with this issue. Specifically, even if there at one point were useful information, the links are not working anymore.

I created another issue, so if there are any good solutions, the rest of the conversation can be continued here:



Edited by Deep_Blue
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Deep_Blue
      Referring to comments in here, I'm looking for a solution to the font issue in the Icon Editor.
      Selecting different fonts does not seem to change the font in the Icon Editor, specifically in the Icon Text tab input.
      I've had no luck playing with the Tools=>Options=>Environment=>Linux=>Use pixel-based font sizes, it seems like whatever I select, the font won't change at all.
      This leads me to believe the issue is with the icon editor and the way it loads the fonts in Linux. I know that it works in Windows, but in Linux it seems as if the Icon Editor always defaults to a same font.
      It does change, but for the worse if I select any of the builtin(?) fonts, LabVIEW Application / LabVIEW Dialog / LabVIEW System - in the Icon Editor Properties.
      I've tried most of everything I found from internet plus then some. I've rebuilt the font cache, copied the small fonts .ttf file from windows etc. so I'm thinking the easy fixes are already exhausted.
      Environment: LabVIEW 2016 on OpenSUSE Leap 42.3.
      So, looking for help in LAVA forums for this.
    • By Antoine Chalons
      I'm starting to use LabVIEW 2020 Sp1 on OpenSuse 15 and the event structure editor - I mean the dialog to add / edit handled event - seems to have localization issues.
      Also, a difference from Windows LV, if a constant is connected to the timeout terminal, LV requires that you handle the timeout event... weird.
      Is it normal / known to have these "issues"?
    • By Óscar Gómez
      In a few days my team and me will start a project and I'm a little anxious because I've never work with PXI Systems... If anyone want to tell me a tip, recommendation or something about your experience with this systems, you'll welcome. I'm one of the developers in the crew!.
      I've experience with cRIO and cDAQ.

    • By peterp
      We're about to re-structure our VI source tree and therefore I'm looking for a way to automatically edit/change the VI icons as well. To do so, I want to open all VI's and change the icon text as well as add a new icon layer (on top) and then save this VI (perhaps also rename it, move it to another location ...) The only problem I have - I can (with help of Icon editor API) open the existing VI, get the icon data (separate entries for text, different layers, ...) and adjust them to new informations/texts/icon layers. But it is not possible to write back these changes to existing VI, I can only create a new VI with this data. Or I can overwrite any old icon settings by passing a new icon, loosing all different icon layers and separate texts.
      Is there any way to edit an existing VI Icon without loosing the existing icon texts/layers? I even tried to open the original icon editor via script and do the edits with "SendInput" remote control of it's user interface. But didn't find a way to open the icon editor on first hand :-(
      So any ideas highly appreciated!
    • By NIKLIVE
      Hello All,
      I am developing the application for Linux using LabVIEW For Linux under openSUSE 12.1 & 11.4 versions.
      My application would be a stand alone application running on the system.
      What I want to achieve is :-
              a). An application which would serve the tasks defined by user and will do that tasks continuously. Here this system with LabVIEW application will be acting as the Server.
              b). Another application which would act as user interface to client for configuring the tasks & this tasks will be sent to Server System as mentioned in point no. a. Here the LabVIEW application will be acting as User Interface Client.
      Now my Questions are:-
       1. What is the bare minimum requirement by the LabVIEW application from the Linux OS to run the LabVIEW application without interface or X window in Linux or the LaBVIEW application in the console format in Linux.
        2. What is the bare minimum requirement by the LabVIEW application from Linux OS to run the LabVIEW application with LabVIEW GUI interface.
      In above both system is not considered as for development, considered as only for deployment point of view. Development System will be different.
      Please give your valuable suggestions or help or guidance if anyone has done this before.
      Thanks & Regards.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.