Jump to content

paul_cardinale

Members
  • Content Count

    39
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by paul_cardinale

  1. Ok. As an alternative, is there a way to get the tab key to function as a tool selector on a block diagram that's in a SubPanel of a running VI? (It seems that the VI that owns the SubPanel is swallowing the keystrokes).
  2. I want to turn AutoTool on. Shift-Tab toggles AutoTool on/off. That would be useful if there is a way to check the state of AutoTool.
  3. Is it possible to programmatically change the inheritance of a LV class?
  4. I'm working on a test executive framework (for both test execution and development). The test step editor places the block diagram of a test wrapper VI in a SubPanel. It works fine, but when the framework is running, within that panel, you can't change tools by tabbing. I want the test executive to turn on AutoTool selection so the test engineers using it won't have to.
  5. Thanks for the reply. Close, but that will just toggle the state. I need to set the state to ON.
  6. Is it possible to programmatically turn Automatic Tool Selection on & off? I found a ToolNumber property, but it always throws error 1028 (LabVIEW: (Hex 0x404) Attribute selector is invalid). I have no idea what that means.
  7. If you have a malleable VI (.vim) inside an XNode, and an instance of that .vim has a declined frame of a type specialization structure, and inside that declined frame you call a VI owned by the XNode, and you have a build spec that copies and renames the XNode, Then that renamed copy of the XNode will be broken because the item in the declined frame isn't properly linked.
  8. Is this what you are trying to do? My Script.vi My Template.vi Setup Static VI Ref.vi
  9. I'm pretty sure that you've built your block diagram incorrectly. Just do it right and it will work fine. (Since you didn't provide any code, I can't be more specific than that.)
  10. Version 1.0.0

    82 downloads

    I think I've finalized my example for the XNode UpdateState ability. This is a very important ability. Failure to properly manage the update process can have dire consequences.
  11. View File UpdateState Illustration I think I've finalized my example for the XNode UpdateState ability. This is a very important ability. Failure to properly manage the update process can have dire consequences. Submitter paul_cardinale Submitted 05/14/2019 Category XNodes LabVIEW Version 2018 License Type BSD (Most common)  
  12. When you are building a source distribution, if you run out of disk space while it's trying to write an XNode ability, it will throw Error 4 (End of file encountered), which is confusing. It should throw Error 9, disk full.
  13. I've discovered that it's best not to put XNodes inside of XNodes (watch out for the NI XNodes like the Error Ring). If VI "A" depends on XNode "B", and XNode "B" depends on XNode "C", then if you save VI "A" for a previous version of LabVIEW, within that previous version, all instances of XNode "C" will be broken. The attached tool will dig through an XNode looking for dependencies on other XNodes. Check for Nested XNodes.vi
  14. Version 1.0.0

    42 downloads

    Here are some of my XNodes, packaged by Brian Hoover.
  15. View File paul_cardinale_xnodes-1.2.0.6.vip Here are some of my XNodes, packaged by Brian Hoover. Submitter paul_cardinale Submitted 04/15/2019 Category XNodes LabVIEW Version 2018 License Type BSD (Most common)  
  16. Try this. Windows User Login 2017.zip
  17. This works, but it uses a private property. Brs Btn Filter.vi
  18. As far as I can tell, lvstring.rsc is the only thing that contains "APP_SC_OPEN_EDITOR_WIZARD´╗┐".
  19. A long time ago (maybe around LV 7) I created a VI that was just a set of property nodes: One for every class (that I knew of), each node having every possible property. I think that when I created it, that property wasn't deprecated. All_Methods.vi All_Properties.vi
  20. And that support would likely consist of: "Don't try to use that thing. It's broken". In general, there isn't an obligation to support undocumented features.
  21. Is there really a need for that thing? If so, it wouldn't be very hard to create it as an XControl .
  22. Have you ever wanted to create an XControl that has a Latching mechanical action? For a long time I thought it was impossible because there's no event that occurs when the block diagram terminal is read. But it can be done by launching a background task that monitors the value in the wire connected to the terminal. See attachment. Latching XControl.zip
×
×
  • Create New...

Important Information

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