Darren

I'm not aware of any intentional changes in LabVIEW 2016 that would cause this. Please post the question to the LabVIEW forum on ni.com so an AE can investigate the issue and file a CAR if necessary.

6 minutes ago, hooovahh said:

So on the topic of weird LabVIEW stuff I had a few today.  I noticed a couple my quick drop functions not dropping what they should be.  Now this might just be a result of my custom quick drop shortcuts, but I don't have any shortcuts for the Copy or Delete functions.  I recorded my oddness here.  Anyone seen anything like this?

Nope, I've never seen that before. You specify the name of a primitive, the thing that gets put on your cursor looks like a Place VI Contents VI of some kind, but then it drops a constant? Go home LabVIEW, you're drunk.

Just now, smithd said:

My problem is that it regularly fails to send the logs up, even when I'd like it to.

Maybe zip up all the logs every once in a while and send them to an AE? They're located here:[LabVIEW Data]\LVInternalReports\LabVIEW

4 hours ago, shoneill said:

How does NI propose we document these problems without sending a complete VM with LabVIEW installed AND complete source code for our project?  Sometimes these problems just get swallowed whole by the inconveneice of trying to demostrate their existence.

I don't have a good answer for this. I run into the exact same issues, and I work at NI! For a while I would file CARs with a [hard to reproduce] tag on them, but I don't think anything ever came of those. I've heard of customers actually visiting NI and bringing their entire setup to get an AE to spend days troubleshooting issues like this, but I think that's overkill in almost all cases.

One thing I can say...I've heard customer sentiment that it's not worth the time to submit NIER crash reports, but that's absolutely *not* true. With each LabVIEW release since NIER's debut, we've fixed *several* crashes as a direct result of the crash reports that were sent in. So continue submitting crash reports (and attaching code where possible and appropriate), because improving stability by solving NIER-reported crashes is something we're committed to with each release.

On 7/19/2016 at 7:08 PM, John Lokanis said:

Why does LabVIEW (almost always) crash when trying to undo the Remove and Rewire and the Insert Multiple Wires QD shortcuts?

On 7/21/2016 at 3:25 AM, shoneill said:

Crash when undoing QD. QD is buggy or is using unstable methods.  We've had several cases of QD shortcuts creating corrupt control references which ended up costing us days of debugging to find.  Random crashes and general instability ensued.

I feel confident in claiming that I use Quick Drop more than anyone on this planet. I use these shortcuts (Remove and Rewire, Insert) dozens of times a day. I've never seen the instability y'all are talking about. No crashes, no "corrupt control references". I've also never seen a CAR reported on these issues either.

I'm not discounting the fact that y'all are experiencing these issues. Believe me, I hate it as much as anyone when the car repair guy tells you that there's no way your automobile can be malfunctioning in the way you describe. But if y'all are seeing these issues as frequently as you claim, why have I not received a bug report that I can investigate? I realize that it's sometimes hard to get things into a reproducible state that can be reported. But hopefully y'all also realize there's not much I can do when the first I hear of these issues in 8 years of the feature's existence is on this LAVA thread.

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.