Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by nhollenback

  1. I'm assuming you've read the tasks & objectives... A good start is to go over those and go back over your LV manuals. Make sure that you fully understand all sections in the manual that are referred to in the tasks & objectives.
  2. Nice summary!! I think everyone would concur on the need for a defined term. We used to have LV2-Style globals, action engines, VIGs, USRs and now we simply have FGVs Here is a thought from a discussion I had last night with someone who knows nothing about LabVIEW. Perhaps in the quest for the perfect "name" we focus less on OOP and more on a name that reflects the benefit of the technology. For instance, the dynamic dispatch just rocks. In essence we now have intelligent wires. What if we follow that line of thinking and see what pops. Perhaps I'll have a chance to return to last night's conversation. Regardless, "object reference" was in several comments above. I tend to make the mistake of overly tying DVR with LVOOP when much of the LabVIEW community will use them without classes. I will check "on high" with the "big wigs" and at least weave a few paragraphs into the Advanced Architectures in LabVIEW course.
  3. So, I think the object is the entity that is actually created at runtime. And the reference would be to the object. So as Jim Kring said, object reference is the best technical term. The class refers to the collection of the .lvclass file, with the definition of the private class data, and the methods that act on that data. And, I think that with the maturity and prevalence of LVOOP, we are at that stage where we can drop the term "native." When I use the term class, it now implicitly refers to LVOOP So perhaps it is VOOP and VOOP'R. And since when did you shy away from silliness? (I probably not doing a good job of getting an invite to the editorial board for your white paper)
  4. Thanks! My sentiments exactly, you just beat me to the reply! I specifically heard at NIWeek that we could get DVR now with out names, or wait for a later release to get DVR and the names. I am glad we have DVR now and will patiently wait for the names. And I want this flexibility, even if someone may make a mess of it in their code. BTW - I don't TIVO, or DVR - I Hulu But cans't thou post to LAVA while the Missus is watching TV?
  5. One of the purposes behind "friends" is to tighten the relationship (pun intended) between XControls (a type of library) and LVOOP classes. So now there is greater protection in setting up an XControl as the UI for the class data. Prior to this, the XControl would have to access the class data through public VIs. As such any other VI could access the data through those public VIs. Now, the class can declare the XControl as the friend. Thus there is protection of the class data for anything other than the XControl friend (or other descendants through protected methods). Hope this helps.
  6. I concur, it is an object reference. But... I like acronyms and we've needed one for this amazingly powerful toolset (LVOOP and now the DVR). Why not just VOOP. And when I'm coding it I'm VOOPing. And those who are real good at it are SOOPer VOOPers. And then LAVA can be come LAVOOPA. Okay, maybe it's just an object reference
  7. Ditto - and on Jim Kring's suggestion, I know keep tub crayons in the shower. Now I need a way to easily capture ideas when I'm out for a long run.
  8. But if I'm going to put the DVR in the SEQ, then I will just bypass the DVR and just use the SEQ And I am TIVOless and hope to remain so
  9. Looking forward to it and happy to do any testing!
  10. I recommend contacting Endevo directly. I would fully expect a release reasonably soon. As you know they still include some very nice UML to LV and LV to UML code generation features. Best, N
  11. Mark is correct. Your first step is to fully understand the Producer/Consumer with Events design pattern that is in the templates browser. (Select File>>New... ). I highly recommend the Basics 1 &2 and Intermediate 1 courses from NI - no I don't work for them . These issues are addressed in the B2 and I1 courses. I hope this helps! Best, N
  12. Me too! But I really want named DVRs. Maybe next release.
  13. I really liked the Desktop Execution Trace toolkit. It identifies references that are not closed at run time. When I used it, the only references that were used in the code were for queues. I was very impressed by this feature. But, I cannot speak for every other entity in LabVIEW that may open a reference (ie. property node that might open a reference to a front panel). Also, I used it in the Dev system. So you may want to return to your source code to identify the problem. Also again, I'm pretty sure you would have to upgrade to 8.6 (or 2009 now) and it comes at a fee My advice - check with your local NI Sales Rock Star. And Mark above also has some great ideas!! Best, N
  14. Hi Tomas, I have worked on several DSC projects but have not experienced this yet. First, how are you deploying the shared variables? Second, can you provide some additional information. How did you determine that you had to do the reinstall to get the SVE working again? What other options did you try? What did you see when you launched the Distributed System Manager? Also, the Colorado LV User Group (ALARM - Advanced LabVIEW Architects of the Rocky Mountains) has spent some time with NI R&D at a recent meeting and we'll be continuing some technical disucssions next week. Check out our community page for more info: http://decibel.ni.com/content/groups/alarm . The current plan is to allow others to remotely join the May 7th meeting. Nancy
  15. QUOTE (Anders Björk @ Apr 6 2009, 10:05 AM) Is your question directed at the specific use of a VI Callback? Or is it related to determining the appropriate event for the event structure. If it is the latter, perhaps you should use cursors and create an event for the Cursor Release when the user releases the cursor on the point in question (unless someone else has a better idea). If it is the former, what is the scenario that is driving the use of the VI Callback as opposed to a standard Producer/Consumer type design pattern? Nancy
  16. My LabVIEW Basics II class is quite pleased that they have destroyed LabVIEW productivity world wide. As they are the ones who tipped me off. And I just happened to show them LAVA after you made this post. :thumbup:
  17. My LabVIEW Basics II class is quite pleased that they have destroyed LabVIEW productivity world wide. As they are the ones who tipped me off. And I just happened to show them LAVA after you made this post. :thumbup:
  18. QUOTE (Eugen Graf @ Jan 5 2009, 03:25 PM) Perhaps the new feature in 8.6 that allows you to write an object to xml is what you need.. http://forums.lavag.org/What-s-new-for-Lab...-86-t11549.html
  19. QUOTE (Ben Zimmer @ Jan 4 2009, 04:50 AM) Hey Ben, I might have some bandwidth for this. And as I'm starting a FIRST Lego League at my son's school in a few months, the timing is perfect!
  20. Your best source for exam preparation is the LabVIEW Basics 1 and LabVIEW Basics 2 manuals. If there is anyway to borrow these, do so. Pay close attention to the quiz questions at the end of each lesson. These are similar to what you might find on an exam. It's important to prep with NI material, because NI writes the exam and you want to become familiar with the terminology that they use. If you can't get the manuals, scour ni.com for study aids and the practice exams. Best of luck!!!
  21. QUOTE (normandinf @ Dec 2 2008, 08:07 AM) LOL - and I like the one on good wine!!!
  22. QUOTE (D. Ackermann @ Dec 2 2008, 08:31 AM) Dermot - what is the overall big picture? Will this be programmatically changed periodically? Will you need to detach a database at the end of a test? In my 8.5 DSC application, we first called "Delete Process" before we created the new database. We ran into a few issues that were mostly resolved. Later today I'll dig up the old code and see what else we did that may help you. Make sure you thoroughly test this!
  23. Your methodology is exactly what we teach in the LV Advanced I course. And I'm not aware of any other solution at the moment (though I am not completely up on anything that may be in 8.6 ). Your solution really is the only way to do it. But, are you also modifying the cluster in the Convert State for Save Ability. Just redefine the cluster with out the ref before you save the VI and then do the reverse on the Init. I'm teaching LV Adv next week, so I'll try to reproduce your error (Xcontrol remaining in memory) and get back with you. I'll also look at the event name issue on some of my XControls. But personally I think your best shot is to stick with the dead chicken! :thumbup: Nancy
  24. Hi Jim, I have a friend who lives and breaths System Engineering and writing and refining requirements and he recommends the following text: "Writing Better Requirements" ISBN 0-321-13163-0 But that is just a book - consider starting that conversation with crelf! Best of luck!
  25. Does anyone have LabVIEW GUI: Essential Techniques? What is your take on the book? BTW - is available on Amazon for $234 :thumbup:
  • Create New...

Important Information

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