Micro-Nuggets !!! ~~~~ Post 'em if you got 'em

[Broken_Arrow]

I've made a simple VI that makes a chart based on a set of interpolation points. In other words, a scaling chart for Input vs. Output, or vice versa. You can make the chart as fine or course as you want with the "Step Size" control. Also lookup individual points along the range.

This also shows some Excel stuff. It throws the chart into Excel and leaves it open for your use.

[Broken_Arrow]

Screenshot for above ap.

[Darin.K]

Here is something I had forgotten and relearned today.

To open a VI from the palette I usually drop it onto some unsuspecting BD, double click and hopefully remember to go back and delete it.  If you hold down Ctrl while you right-click to get the palettes you will open the selected VI and not drop it onto the BD.

[SteveChandler]

Maybe this is not a micronugget but more of a piconugget.

The Software Validation Toolkit includes the Desktop Execution Trace Toolkit, Unit Test Framework and VI Analyzer Toolkit. The validation toolkit now ships with LabVIEW 2011 Developer Suite. I think the developer suite is only a couple hundred dollars more than the professional version.

If you have not seen it check it out under Tools/Profile/Trace Execution.

[John_Deans]

Good One! I have wanted to use the Quit LabVIEW vi only when code is compiled up to mow I have us the conditional disable structure but it was a pain when I forgot to change it

[Hornless.Rhino]

---

@broken Arrow wrote:

Screenshot for above ap.

---

What did you use to make that torn paper effect in the screenshot?

[Broken_Arrow]

---

@Hornless.Rhino wrote:

---

@broken Arrow wrote:

Screenshot for above ap.

---

What did you use to make that torn paper effect in the screenshot?

---

That made me LOL. My admittedly undeveloped and unexplained Micro-Nugget about Polynomial Interpolation has finally received some attention!

For screen captures with effects, I use Snagit

[Broken_Arrow]

Hello all

I would like to share a VI that demonstrates a few Ideas regarding a Searchable Class Name Hierarchy. It is my hope that the VI will demonstrate a few Micro-Nuggets, some topics which have risen lately in different forums.

After downloading the folder, the main VI to open is named VI Server Class Hierarchy Browser.vi.

Micro-Nugget: Use a Combo Box as a quasi auto completing search box. See the Search box in the main VI.

Micro-Nugget: Populate a Tree from a multi-line string using an “indent” number to configure Parent Tags. See the “Pop Tree” case on the main VI. (Code should be more scalable if it is to be used on anything but known hierarchy levels, and yes, it uses local variables where other methods would work, but I'm personally ok with a W2TRO local in this case).

Nano-Nugget: “Export” to Notepad. See the “Export” event in the Events case.

Pico-Nugget: Drag and Drop from a Tree (it's basically nothing, really, just wanted to point out how easy it is and how well it works with a tree - with no effort).

As a “freebie”, you’ll find the Class Name Hierarchy in a text file named Prop List text numbered.txt. The program doesn’t use this file, although it could

SCREENSHOT ---------------------------------------------

[SteveChandler]

Now we just need a mega-nugget on building this inth the RCF in order to drop the constants on the BD.

[tst]

---

@Steve Chandler wrote:

Now we just need a mega-nugget on building this inth the RCF in order to drop the constants on the BD.

---

If you want to drop VI server class constants, you can use the class browser (Ctrl+Shift+B), which does essentially the same thing, but also allows you to drag constants to the diagram. Personally, I don't use it, probably because it's too much of a pain. If you vote for this idea, that should simplify this process somewhat - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-Intellisense-support-to-the-property-node/idi-p/15.... The idea mentions the constant near the end.