Jump to content

Font issue in icon editor


Deep_Blue

Recommended Posts

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.

Edited by Deep_Blue
Link to comment

Thank you for posting this.  It's very helpful and informative.

I was noticing icon font issues in LabVIEW 2020 Community Edition for Linux, so it doesn't look like NI has fixed (or knew about) the issue in LV 2020 for Linux either.

  • Like 2
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.

Guest
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
      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?
    • By Antoine Chalons
      [cross-post]
      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 Mark Balla
      Mark Balla Icon editor V2.7
      December 2020
      Author: Mark Balla
       
      Description:
      This is a text based vi icon editor 
      The purpose is to help quickly create text base icons.
      The editor can be used in place of the standard NI icon editor or as a stand alone vi. see instructions.
      Version 2.7
      Updated font table to recognize the standard "Small Font" letters used by the NI icon editor. This will improve the OCR function when importing icons generated by the NI Icon editor.
      Version 2.6
      Added quick drop code to allow the user to switch between NI and custom editor.
      QD_Swap Icon Editor.vi and support folders will be placed in the LabVIEW quick drop folder
      ..\National Instruments\LabVIEW 20XX\resource\dialog\QuickDrop
      To switch LabVIEW to a custom icon editor that uses the lv_icon.vi set a shortcut key to call the QD_Swap Icon Editor.vi. Ctrl-Space Ctrl-<<assigned letter key>>
      To switch LabVIEW to the NI icon editor that uses the lv_icon.lvlibp use the same shortcut key with the Shift key
      Ctrl-Space Ctrl-Shift-<<assigned letter key>>
      Version 2.5
      Fixed install bug where lv_icon.lvlibp was not being renamed after LV 2016
      2.5 was set to 2017 or later.
       
      Instructions:
      LV 2017 to LV2020 + Ver 2.7 +
      Here is the intended process.
      Download package from LAVA Install Package Package will install MB icon editor files Package will install QD_Swap Icon Editor.vi in the QD plugins folder Package will copy the lv_icon.lvlibp And rename it to COPY_ lv_icon.lvlibp Package will delete the lv_icon.lvlibp Popup will show stating you are using the custom editor. Open LV Open QD, click configure and select the  Ctrl-Key Shortcut Tab at the top Assign a control key to the QD_Swap Icon Editor and click OKWhen you select Ctrl-Space  Ctr-<<Assigned Key>> the QD vi will setup the IDE to use my custom editor. The vi will verify there is a copy of the  lv_icon.lvlibp And if not create it. The vi will delete the lv_icon.lvlibp From the  ..\National Instruments\LabVIEW 20XX\resource\plugins folder When you select Ctrl-Space  Ctr-Shift-<<Assigned Key>> the QD vi will setup the IDE to use the NI editor. The vi will copy the COPY_lv_icon.lvlibp and rename the copy to lv_icon.lvlibp LabVIEW will use the lv_icon.lvlibp If it sees it in the plugins folder. If it does not see the lv_icon.lvlibp It will call the lv_icon.vi which is the name of my icon editor.
      LV 2010 to LV 2016 Ver 2.4
      Install using JKI VI Package Manager
      LV 2009 Ver 2.3

      1:Rename the curret LabVIEW 2009 Icon editor LabVIEW 2009\resource\plugins\lv_Icon.vi to a different name so it will not be overwritten.

      2: Place the three files (lv_icon.vi, color templates.bin and the folder lv_icon_Subvis) in the LabVIEW 2009\resource\plugins directory.
      The next time the icon editor is called LabVIEW will use the lv_icon.vi instead of the standard one.
      There is a button on the editor that will allow you to use NI's editor (Old editor not the new one) when a text icon is not desired.

      For LabVIEW 8.2 Use the "MB Icon Editor_V2.3_LV82.zip" file
      For LabVIEW 8.5 Use the "MB Icon Editor_V2.3_LV85.zip" file
      For LabVIEW 8.6 Use The "MB Icon Editor_V2.3_LV8.6.zip" file
       
    • By Mark Balla
      View File Mark Balla's Icon Editor V2.7>= LV2017
      Mark Balla Icon editor V2.7
      December 2020
      Author: Mark Balla
       
      Description:
      This is a text based vi icon editor 
      The purpose is to help quickly create text base icons.
      The editor can be used in place of the standard NI icon editor or as a stand alone vi. see instructions.
      Version 2.7
      Updated font table to recognize the standard "Small Font" letters used by the NI icon editor. This will improve the OCR function when importing icons generated by the NI Icon editor.
      Version 2.6
      Added quick drop code to allow the user to switch between NI and custom editor.
      QD_Swap Icon Editor.vi and support folders will be placed in the LabVIEW quick drop folder
      ..\National Instruments\LabVIEW 20XX\resource\dialog\QuickDrop
      To switch LabVIEW to a custom icon editor that uses the lv_icon.vi set a shortcut key to call the QD_Swap Icon Editor.vi. Ctrl-Space Ctrl-<<assigned letter key>>
      To switch LabVIEW to the NI icon editor that uses the lv_icon.lvlibp use the same shortcut key with the Shift key
      Ctrl-Space Ctrl-Shift-<<assigned letter key>>
      Version 2.5
      Fixed install bug where lv_icon.lvlibp was not being renamed after LV 2016
      2.5 was set to 2017 or later.
       
      Instructions:
      LV 2017 to LV2020 + Ver 2.7 +
      LV 2010 to LV 2016 Ver 2.4
      Install using JKI VI Package Manager
      LV 2009 Ver 2.3

      1:Rename the curret LabVIEW 2009 Icon editor LabVIEW 2009\resource\plugins\lv_Icon.vi to a different name so it will not be overwritten.

      2: Place the three files (lv_icon.vi, color templates.bin and the folder lv_icon_Subvis) in the LabVIEW 2009\resource\plugins directory.
      The next time the icon editor is called LabVIEW will use the lv_icon.vi instead of the standard one.
      There is a button on the editor that will allow you to use NI's editor (Old editor not the new one) when a text icon is not desired.

      For LabVIEW 8.2 Use the "MB Icon Editor_V2.3_LV82.zip" file
      For LabVIEW 8.5 Use the "MB Icon Editor_V2.3_LV85.zip" file
      For LabVIEW 8.6 Use The "MB Icon Editor_V2.3_LV8.6.zip" file
       
      Submitter Mark Balla Submitted 10/19/2009 Category LabVIEW IDE LabVIEW Version 2017 License Type BSD (Most common)  
    • By ChuckBorisNorris
      Hi All, Long-time lurker, first-time poster here.
      As the title (hopefully) implies, I have an issue connecting to a database I've created. 
      The problems started this week after coming back to look at the project after ~3 months. I know I had to repair my Office 365 installation last week and I'm wondering if that could be the cause but other than that I'm at a complete loose end.
      Microsoft support say it's a LabVIEW issue, NI support say it's an MSDN issue. The official NI forum, after looking at similar posts, was even less helpful. So I thought I'd come and see if the nice guys at LAVA had experienced a similar issue.
      I'm aware that the error code is a generic one and has multiple causes but I am simply writing a "SELECT [column] FROM [table];" statement to an 'Execute Query' vi. The error returned from my sanity checking vi is: 
      (Code -2147217900) NI_Database_API.lvlib:Conn Execute.vi->Untitled 1<ERR>ADO Error: 0x80040E14
      Exception occured in Microsoft Access Database Engine:  in query expression '[UserID]'. in NI_Database_API.lvlib:Conn Execute.vi->Untitled 1
      The connection string returned is (without line breaks):
      Provider=Microsoft.ACE.OLEDB.12.0;
      User ID=Admin;
      Data Source=T:\PROJECTS\02-ACTIVE\119888 RF Power upgrade\Database\RFPU.accdb;
      Mode=Share Deny None;
      Jet OLEDB:System database="";
      Jet OLEDB:Registry Path="";
      Jet OLEDB:Database Password="";
      Jet OLEDB:Engine Type=6;
      Jet OLEDB:Database Locking Mode=1;
      Jet OLEDB:Global Partial Bulk Ops=2;
      Jet OLEDB:Global Bulk Transactions=1;
      Jet OLEDB:New Database Password="";
      Jet OLEDB:Create System Database=False;
      Jet OLEDB:Encrypt Database=False;
      Jet OLEDB:Don't Copy Locale on Compact=False;
      Jet OLEDB:Compact Without Replica Repair=False;
      Jet OLEDB:SFP=False;
      Jet OLEDB:Support Complex Data=False;
      Jet OLEDB:Bypass UserInfo Validation=False;
      The BD for my sanity check looks like this:

      I'm using LabVIEW 2016 32-bit on a W7 Dell Ultrabook with Access2013 as part of our Office 365 installation. BTW the query executes fine in Access2013. Is that enough info?
      Regards,
      Boris
       
×
×
  • Create New...

Important Information

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