Jump to content

Samuel

Members
  • Posts

    2
  • Joined

  • Last visited

  • Days Won

    1

Samuel last won the day on January 20 2022

Samuel had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Samuel's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare

Recent Badges

1

Reputation

  1. Hi Jim, Great, that works like a charm! Thank you very much!
  2. Hello, I am using the package builder to package a library. I don't want to use the default palette that recreates the folder hierarchy, but group VIs by functions to make an intuitive palette. The library is used to communicate with an instrument, and my target location is the intr.lib folder. I have therefore chosen this folder on the "source File settings" pane. Then on the "palette" pane, I have edited the function palette to include and group the different VIs as I want them to appear in the palette menu. I have also chosen "instrument drivers" in the palette location box, as it is where I want my custom palette to be located. When I install the package, everything works fine, but my library appears twice on the instrument drivers palette: once with the custom palette I created, and once recreating the folder hierarchy of the package. I'm assuming that the second one is automatically included by LabVIEW as it scans the sub-folders in the inst.lib folder and create a palette for this. I have found a workaround which is to physically locate the files in another folder, however this solution is obfuscating and it would be more logical to have the files physically located in the instr.lib folder as well. What would be the best way to proceed? Thanks for your help!
×
×
  • Create New...

Important Information

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