Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. Another option is creating a lv_new_vi.vi in that same folder. This VI will override the behavior of pressing Ctrl-N. You can find the required conpane for the VI on labview wiki somewhere, but I think it's just 4x2x2x4 with an I32 in the upper right. Unfortunately (due to its age as a feature) it has no knowledge of application instances, and thus doesn't work properly when pressing Ctrl-N under different containers in the project window.
  2. This is a C-based dialog, it does not have a G implementation that you can modify.
  3. I don't know of a way to accomplish this. As discussed above, changing a VI with scripting requires the Transaction methods to preserve Undo history. To my knowledge you can't modify a VI with scripting, have that modification not show up in the Undo history, but preserve the previous Undo history.
  4. I recently dealt with this issue when designing the LabVIEW Cloud Toolkit for AWS. I had to create a lot of new error codes, that mostly correspond 1-to-1 with the errors that AWS can return. My ultimate solution was that I had an Excel spreadsheet per class (Core, S3, SNS, SQS, IoT), and a build tool that parsed these Excel files and created a separate error text file for each class.
  5. Assuming you're talking about the Data Type Parsing VIs in LabVIEW 2015 and later, you can read the documentation on them. Or you can watch my Hidden Gems presentation in which I describe some use cases for their predecessors, the VariantDataType VIs.
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. 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 frequent
  11. There is currently no way to reload the error text file contents without a LabVIEW restart.
  12. Laura and I will be there. We're looking forward to seeing everybody again!
  13. 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.
  14. I think ShaunR wrote a .vim that provided the ability to name user events, but it didn't work quite right?
  15. Jeff added 6 .vims to [LabVIEW 2016]\user.lib\macros, including the Norm.vim he mentioned.
  16. There is an undocumented, unsupported API for scripting FPGA nodes. Take a look in this folder and see what you can find: [LabVIEW 20xx]\vi.lib\rvi\ClientSDK
  17. I talk about which references should be closed vs. which ones you don't have to worry about closing in my Brainless LabVIEW presentation.
  18. Assuming you have an easy way to get all the child classes into memory, something like this should do the trick:
  19. 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.
  20. I honestly don't remember making that change. Maybe I did, maybe I didn't. Only Perforce knows for sure.
  21. 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?
  22. We deprecated those VIs in LabVIEW 2015 and created new ones that use error in/error out instead of embedded error handlers:
  23. 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.
  24. 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.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.