LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Does anyone have a list of where stuff goes?

I was going to put together a cheat sheet of where IDE extension items belong or can be.  Then I realized... I probably don't have to go digging for all of it (again) because the Community knows.

 

"The list" would ideally be picked up as a LabVIEW document suitable for pinning on a cube wall next to the LabVIEW Shortcut key.   Items would include;

  • VI Templates
  • Project Templates
  • Project Template Metadata files
  • Icon Templates
  • Icon Glyphs
  • Custom error files
  • QD plugins
  • VIA Tests
  • VIA Custom Configurations
  • Frameworks
  • Custom Probes
  • Tools
  • XNodes
  • Wizards
  • Custom Menus (vi)
  • Custom Menus (control / function Palettes)
  • Menus (Right-Click)

Anything else that doesn't go in LabVIEW.ini. (I hope that I didn't miss more than 50%)


"Should be" isn't "Is" -Jay
0 Kudos
Message 1 of 5
(1,255 Views)

Here you go. A couple of notes:


1. A lot of this stuff is discussed in my Don't Wait for LabVIEW R&D... Implement Your Own LabVIEW Features! presentation: http://bit.ly/dnattlvhooks
2. I think it would be good for this information to be published on the LabVIEW Wiki.

VI Templates (show up in the "New..." dialog)
[LabVIEW 20xx]\templates

 

Project Templates
[LabVIEW 20xx]\ProjectTemplates

 

Icon Templates
[LabVIEW Data]\Icon Templates

 

Icon Glyphs
[LabVIEW Data]\Glyphs

 

Custom error files
[LabVIEW 20xx]\resource\errors
[LabVIEW 20xx]\project\errors
[LabVIEW 20xx]\user.lib\errors

 

Quick Drop plugins
version-specific: [LabVIEW 20xx]\resource\dialog\QuickDrop\plugins
version-agnostic: [LabVIEW Data]\Quick Drop Plugins

 

VI Analyzer Tests
version-specific: [LabVIEW 20xx]\project\_VI Analyzer\_tests
version-agnostic: [LabVIEW Data]\VI Analyzer Tests

 

VI Analyzer Custom Configurations
Assuming this refers to .cfg/.viancfg files, they can go anywhere

 

Frameworks
??? Not sure what this refers to

 

Custom Probes
version-specific: [LabVIEW 20xx]\user.lib\_probes
version-specific: [LabVIEW 20xx]\vi.lib\_probes
version-agnostic: [LabVIEW Data]\Probes

 

Tools (show up in the 'Tools' menu)
[LabVIEW 20xx]\project

 

XNodes
Assuming this refers to any arbitrary .xnode file, they can go anywhere

 

Wizards (show up in the 'File' menu)
[LabVIEW 20xx]\wizard

 

Custom Menus (vi)
??? Not sure what this refers to

 

Custom Menus (control / function Palettes)
[LabVIEW 20xx]\menus (product palettes)
[LabVIEW Data]\20xx(xx-bit)\Palettes (user edits to palettes)

 

Menus (Right-Click)
version-specific: [LabVIEW 20xx]\resource\plugins\PopupMenus
version-agnostic: [LabVIEW Data]\PopupMenus

Message 2 of 5
(1,202 Views)

Thanks Darren 

 

I didn't know about version-agnostic stuff!

Custom Menus VI referred to.*.rtm files that can go next to the vi or in it.

 

Frameworks go to [LabVIEW 20xx]\resource\framework providers\ 

I'm going to guess there is a [LabVIEW Data]\ location as well

 

I have a link to the project template Metadata KB article somewhere and will add it later.


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 5
(1,182 Views)

The stuff in [LabVIEW 20xx]\resource\Framework\Providers pertains to Project Providers, which is an area that I strongly recommend LabVIEW programmers *not* spend time trying to figure out. My afore-mentioned presentation goes into details about why I don't like Project Providers.

The page that details how to write a custom Project Template is here. Interesting, I just re-read the page (I wrote the original 10 years ago) and I had forgotten that there is a version-agnostic location in [LabVIEW Data] for Project Templates. I don't think I've ever seen anyone use that.

0 Kudos
Message 4 of 5
(1,098 Views)

@Darren wrote:

Here you go. A couple of notes:


1. A lot of this stuff is discussed in my Don't Wait for LabVIEW R&D... Implement Your Own LabVIEW Features! presentation: http://bit.ly/dnattlvhooks
2. I think it would be good for this information to be published on the LabVIEW Wiki.


Started a page for it. Not sure how to organize it yet but at least it is started.  https://labviewwiki.org/wiki/LabVIEW_addons 

 

Quentin "Q" Alldredge

Chief LabVIEW Architect, Testeract | Owner, Q Software Innovations, LLC (QSI)
Director, GCentral | Admin, LabVIEW Wiki | Creator, The QControl Toolkit
Certified LabVIEW Architect | LabVIEW Champion | NI Alliance Partner



Message 5 of 5
(896 Views)