Jump to content

Darren

NI
  • Content Count

    539
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by Darren

  1. I talk about which references should be closed vs. which ones you don't have to worry about closing in my Brainless LabVIEW presentation.
  2. Assuming you have an easy way to get all the child classes into memory, something like this should do the trick:
  3. 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.
  4. I honestly don't remember making that change. Maybe I did, maybe I didn't. Only Perforce knows for sure.
  5. 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?
  6. We deprecated those VIs in LabVIEW 2015 and created new ones that use error in/error out instead of embedded error handlers:
  7. 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.
  8. 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.
  9. 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
  10. 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.
  11. 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.
  12. 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.
  13. Ah cool, yeah, that seems like it would work.
  14. 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.
  15. 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:
  16. Here's a Quick Drop shortcut that will do a recursive typedef disconnection: https://decibel.ni.com/content/docs/DOC-37041
  17. 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!
  18. 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.
  19. Feel free to send some sample code to the AEs so they can file the necessary CARs.
  20. Yeah, I can't think of anything else to try. There very well may be a bug with setting key focus on an array element in a floating VI window.
  21. I am not seeing a way to get the key focus to always go to the first element (as opposed to going to the last one that was clicked). I'm also not aware of any documentation on these particular array idiosyncrasies. You need the panel activation if you're running the VI from somewhere other than the panel. For example, if you're on the diagram and you press Ctrl-R, the key focus doesn't take.
  22. First you need to activate the panel. Once you do that, you can set key focus of the array element and it will work.
  23. Unfortunately, the Class Browser (both incarnations...the one you describe, and the one you see when you press Ctrl-Shift-B) is not implemented in G.
  24. The GetType.llb VIs were added in LabVIEW 7.0, and they were used to parse the legacy I16 Array type descriptors. The VariantDataType VIs were added in LabVIEW 8.0, when we switched to using Variants to define data types instead of I16 Arrays. At this time, the internals of the old GetType.llb VIs were updated to use Variants as well. So there's no need to use the VIs in GetType.llb. They are deprecated. And it's a little late in the game, but we are planning on marking them as deprecated in a future LabVIEW version.
  25. This Quick Drop shortcut shows how to do it on Windows (you use the "/select" parameter), but I'd like to know if there's a way to do it on Mac/Linux: https://decibel.ni.com/content/docs/DOC-22461
×
×
  • Create New...

Important Information

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