Darren

There is currently no way to reload the error text file contents without a LabVIEW restart.

On 6/13/2016 at 2:11 PM, Darren said:

Jeff added 6 .vims to [LabVIEW 2016]\user.lib\macros, including the Norm.vim he mentioned.

Oops, spoke too soon. I saw these in an internal build image and assumed they were in the installer. They are not, so they will not be in the LabVIEW 2016 install. Sorry to get y'all's hopes up.

2 minutes ago, Aristos Queue said:

I don't understand. Why would you expect VIMs to have changed anything with respect to events? This is an edit-time feature, not a run-time feature. Can you explain the link that you're seeing? 

I think ShaunR wrote a .vim that provided the ability to name user events, but it didn't work quite right?

1 minute ago, ShaunR said:

But the big question is "do my named events work properly now?"

I have no idea.

On 6/10/2016 at 5:38 PM, jacobson said:

Dang, couldn't find this structure in the last LabVIEW build and got 0 hits when trying to find more information about it internally. The thought had crossed my mind that JeffK just made this all up for his own entertainment and while I would be a bit sad, I would definitely respect that.

I guess I'll have to wait patiently with everyone else until release.

Jeff added 6 .vims to [LabVIEW 2016]\user.lib\macros, including the Norm.vim he mentioned.

I talk about which references should be closed vs. which ones you don't have to worry about closing in my Brainless LabVIEW presentation.

I've noticed similar behavior for other abilities. For example, if you click the drop-down on an Error Ring, then click cancel, your VI still gets a dirty dot even though you didn't change anything. I don't know of any way around this behavior.

Aha. You've deprecated it to a warning. You are a legend

I honestly don't remember making that change. Maybe I did, maybe I didn't. Only Perforce knows for sure.

Do they throw an error 4 when they read the entire file? (one of my pet peeves)

Other than the error input/output, the functionality of the VIs didn't change. I'm not seeing an error when reading an entire file. I am seeing a *warning* 4 when specifying a number of rows to read greater than the size of the file, is that what you're referring to?

Note also that some of the other LabVIEW VIs have the general error handler inside them, "Write to Spreadsheet File.vi" and "Read from Spreadsheet File.vi" for example.

We deprecated those VIs in LabVIEW 2015 and created new ones that use error in/error out instead of embedded error handlers:

I don't know of a way to do this. If somebody else does, please post here, as it's a gap in the functionality of the Quick Drop VI Server Rename shortcut (ships with LabVIEW 2010 and later) that I'd like to fill.

There are undocumented, unsupported scripting APIs for the FPGA nodes located here:

vi.lib\rvi\ClientSDK\Core\Script

I have talked about this API a few times on the NI forums, as have others. You can google that vi.lib path to find some of the posts related to this topic.

The Mouse Position value passed in to your plugin gives you the location of the right-click.

Future questions about right-click plugins should be posted to the community page here: http://www.ni.com/lvmenus

This is a demo from the presentation Stephen and I gave at NIWeek 2015 regarding the new right-click plugin feature in LabVIEW 2015. You can get the slides for the presentation, along with all the demos (including the spell checker), and a demo script, here:

http://www.ni.com/lvmenus

Note that the spell check right-click demo requires that you have the VI Analyzer Toolkit for LabVIEW 2015 installed, as it uses the dictionary provided by the VI Analyzer's Spell Check test.

Thanks for the rec. I've been looking for a cheap tablet to run LabVIEW apps on, this one looks like it will fit the bill, so I snagged one from the online microsoft store.

Monday

Inspecting Your LabVIEW Code with the VI Analyzer - 3:30, room 17B

Tuesday

Augmenting Right-Click Menus in LabVIEW 2015 - 3:30, room 16B (co-presenting with Stephen Loftus-Mercer)

Inspecting Your LabVIEW Code with the VI Analyzer (encore) - 4:45, room 16B

The VI Analyzer presentation has already been recorded here, and all the demo/slide materials are currently posted here. So my feelings won't be hurt if y'all go see somebody else's presentation (like Norm's) and just watch my recording later.

Did you see how I was trying to stop it? The front panel reference dies when you close the probe and the property node throws an error.

Ah cool, yeah, that seems like it would work.

That won't work if the probe VI doesn't update its FP until called again.

I tried it, and the probe UI will update when the Fire and Forget VI runs, even if the probe itself is idle. I saw my probe happily incrementing while its owning VI was idle.

The biggest snag will be figuring out how to stop the Fire and Forget VI. It continues running even after the probe UI is closed.

This is the approach that I've seen taken for this issue...you have to do all the work you would normally do in the NI.LV.Dialog app instance in the app instance that owns the VI from which you launched the Tools utility:

Here's a Quick Drop shortcut that will do a recursive typedef disconnection:

https://decibel.ni.com/content/docs/DOC-37041

I am not aware of a way to script a dotted property. It's been one of my top requests for scripting for years now, because of how frequently I use the Ctrl-Shift-B shortcut in Quick Drop to rename a property/invoke node...I can't set "Label.Text", and it drives me crazy!

Note to self: lob softballs at AQ's inbox early in the day, so he'll be happy when I ask him tougher questions later. 

Got it.