LabVIEW Scripting Main Board

[TCPlomp]

Anyone knows how to activate scripting for LabVIEW 2009?

The installer says nothing needs to be changed somehow.

Ideally I would like to keep my scripting license for 8.6 active.

Ton

[Jim_Kring]

I think that you just activate scripting for 8.6 and it works in all versions of LabVIEW.

[TCPlomp]

JimKring wrote:

I think that you just activate scripting for 8.6 and it works in all versions of LabVIEW.

Unfortunatly not, I tried hacking the 8.6 script file and got an entry in the 2009 License manager but could not get it correctly activated.

Come on NI, you even mentioned scripting in the promo video, so please provide a scripting file to use with LabVIEW 2009.

Ton

[TrevorChristman]

There is a specific scripting installer for LabVIEW 2009.  This installer has been created and is currently traveling down the pipe to be placed on the NI-Labs download page.

You can either wait for it to be posted, or email me directly to request a copy (trevor.christman@ni.com).  If you're in Austin for NI-Week, email me your contact information and I'll deliver a copy in person.  I'll be at the Austin Convention center this afternoon and most of the day tomorrow.

However you get a copy of the installer, please avoid posting it online.  Whenever we release an updated version of the installer, we'd like to avoid having to track down lots of outdated copies.

[tst]

The scripting installer for 2009 seems to have been posted.

[Darren]

I just posted a helpful image illustrating subVI connector pane terminal order.

Terminal Order of SubVI Connector Pane Patterns

-D

[njg]

Unexposed property node elements for numeric fixed point...

As of LabVIEW 2009 there is an exposed property node element to set the representation of a numeric to Fixed-Point; however, the elements to set the specifics of the Fixed-Point type (signed, word length, etc.) are hidden by default.  There is an unofficial method to expose these extra elements so I'm not writting for help, but rather to point out that these elemnts probably should be exposed by default.

[TrevorChristman]

njg,

  Thanks for the heads up.  I'll make sure those methods get evaluated for becoming public in LV2010.

[viScience]

Has anyone used the Get/Set Tag methods on a control or panel?  I am thinking about using them

for storing async process references but would like to hear from others about any caveats in using them.

[Darren]

If you use the Get/Set Tag methods directly, you run the risk of clobbering internal NI tags.  I recommend you check out the VIs in vi.lib\UserTags, which wrap the Get/Set Tag methods, but also namespace them to avoid conflicts with internal NI tags.  The vi.lib\UserTag VIs are available in LabVIEW 8.6 and later.

Edit:  I just noticed you were planning on storing reference information in the tags.  The VIs in vi.lib\UserTags do not support this (they will return Error 1 if you attempt to store LabVIEW Class or Refnum data in a tag).  I don't remember the exact reasons why these data types aren't supported, but I think it has to do with possible data corruption.

-D