Jump to content
News about the LabVIEW Wiki! Read more... ×


  • Content Count

  • Joined

  • Last visited

  • Days Won


Darren last won the day on January 14

Darren had the most liked content!

Community Reputation


About Darren

  • Rank
    The 500 club
  • Birthday 10/02/1977

Profile Information

  • Gender
  • Location
    Austin, TX

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

2,426 profile views
  1. Darren

    Programmatically Set a Property Item

    Thanks for digging this up, Paul. I got it to work for dotted properties of multiple levels (so not only Label.Text, but also things like Terminal.Wire.Terms[]). I'm going to try to update the VI Server Rename plugin for Quick Drop to allow setting dotted properties by using this deprecated property. (?)
  2. You can also use Quick Drop Replace to replace multiple items at once. Select all the controls you want to replace > Ctrl-Space > Type name of new item > Ctrl-P to replace them all.
  3. Darren

    Programmatically Set a Property Item

    I had no idea this existed. I will look into it.
  4. Darren

    Programmatically Set a Property Item

    Correct. Scripting does not support setting dotted properties.
  5. Darren

    Project Template Dependencies Best Practices

    +1 for installing shared dependencies in vi.lib with VIPM packages. Makes this sort of thing much easier to manage than having each project have their own copy of the reuse code.
  6. Darren

    Tree Coords in expand/contract symbol?

    From what I can tell, the Item Close(?) and Item Open(?) events are not private. Maybe they were in a previous LabVIEW release?
  7. Ah, there's the piece I was missing. Thanks for those details. I have filed CAR 711518 on this issue. I agree that it is a significant usability concern that it is so easy to wire to that null reference terminal, have code that doesn't function correctly, and not have an indication as to why.
  8. I'm not sure how you got into this state, I don't see the hidden terminals in scripting. And if you delete those wires, there's no way to get back to the hidden terminals. Also, I got a DWarn when I copied your snippet into my diagram. So I'd chalk this up to some weird corner case/corruption and move on.
  9. Darren

    Connecting Error Cluster to Bottom of VI

    There's also a recording of this presentation available here: http://bit.ly/brainlesslabview
  10. Darren

    Ring Control: event for the current value?

    There's a private 'Operate Menu Dismissed' event that may help in this situation.
  11. Darren

    Variant attributes, Flatten to String

    Can you attach a simple write VI and read VI that demonstrate the issue?
  12. Darren

    Scripting functions for malleable VIs?

    It's impossible to change the label text of a subVI. That's why this works.
  13. Darren

    Scripting functions for malleable VIs?

    Yeah, I think the explanation given to me was that the contents of the .vim file on disk are no different than the contents of a .vi file on disk. So since it's technically not a different file type, they thought it didn't warrant a new enum entry. Kinda like how there's not a "Template VI" entry in the list since .vi and .vit are the same type on disk. I may be misremembering though so don't take this as the official answer.
  14. Darren

    Scripting functions for malleable VIs?

    It may surprise you that this is the best way:
  15. Darren

    Highlight item in Project tree

    You can also press Ctrl-Shift-E from an open VI to select that VI in the project explorer.

Important Information

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