Jump to content

Jeffrey Habets

  • Posts

  • Joined

  • Last visited

  • Days Won


Jeffrey Habets last won the day on May 30 2019

Jeffrey Habets had the most liked content!

About Jeffrey Habets

  • Birthday 05/17/1972

Profile Information

  • Gender
  • Location
  • Interests
    LabVIEW, Photography, Diving, Guitar

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jeffrey Habets's Achievements


Newbie (1/14)



  1. VITech will bring along this uniquely boxed Raspberry Pi. 😊 Completely ready to run LabVIEW programs out of the box.
  2. Great to see the LabVIEW wiki alive and kicking again! Hope to have a bit of time to contribute sometime after NIWeek...
  3. I agree with Rolf, but just in case you need more, you might have a look at this dongle solution for LVRT from WireFlow: http://www.wireflow.se/products/wf2007
  4. http://www.labviewwiki.org/Custom_LabVIEW_configuration_file
  5. Thanks Mark and Dan! Much appreciated.. 14-8-12_06_LabVIEW UserGroup Awards_Challenge of the Champions seems to have the wrong content. This is part of Jack's FTW presentation. Edit: Seems fixed now. Thanks!
  6. It was just around dinner time here, so unfortunately I missed it. Going to watch it now!
  7. I just want to confirm that I'm also unable to see the RSS feeds in Firefox for 1 or 2 weeks now.
  8. Hmmm, you sure.. Especially after a couple of full days of coding LV my hand really hurts. But, to get back on topic.. I agree with AQ that a class is best tested on it's public interface. I can imagine that in some use cases it would be handy to test some of the private parts and for that I think the next best thing is indeed to use community scope and friend VIs or libs. Putting the test VIs in the class can be a real pain, for example when integrating your class in the greater whole. If during integration changes need to be made to the interface of a class member that is used in a test VI, chances are that test VI will be broken, thus your class will and your application too. So your build is broken because of the broken testcode even though all VIs actually used in the application's hierarchy are not.
  9. And when you've done that, Use it! Use it! Really if you do OOP, do yourself a favour and use it. It boosts productivity! And in the next version it even does that for the Actor Framework too! (No, I do not work for them. )
  10. I won't.. I'll keep on breathing.. Hot Texan air for the coming week.
  11. Sounds indeed like cRIO for the deterministic part would fit in perfectly here. And I just happen to know a fine Alliance Member here in the Netherlands that loves this sort of projects and is quite proficient with LabVIEW and cRIO. Hey, that seems to be a link to their site down there..
  12. I'd expect you need to do more then just a simple valid-refnum check to see if a connection is valid and that it would be different actions depending on the protocol that is used. So I would opt for implementing a dynamic dispatch "CheckConnection" method and make it "Must Override" so that each child has to implements it's own. If you're really certain that you can use the same piece of code to check connection for all child implementations, I vote for AQ's solution above.
  13. I'm in too... Just bought my ticket. This did it for me.
  14. My flight out of Austin is Friday 4.00pm so I'll be hanging around some on Friday.
  15. FWIW, you can use popup's in remote panels. Just not system dialogs. If you implement your own popup dialog sub-VI it will also work for a remote panel.
  • Create New...

Important Information

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