Jump to content

jgcode

LabVIEW Tools Network
  • Posts

    2,397
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by jgcode

  1. You do a multiple choice for a CLA recert. There is an example exam on the web.
  2. Should #LabVIEW Service Packs be a separate install and not an upgrade? Chime in @lavag http://bit.ly/i2Uj9U

  3. I subscribed to both forums, but I agree its probably best to keep the thread going over there rather than start here.
  4. Should LabVIEW Service Packs be a separate install and not an upgrade? I want to highlight this thread on the darkside as I think it is very interesting and would like to hear what others think here on LAVA. [/color]Please discuss.
  5. Wow, how long to you have to be programming to be considered 'old' ??
  6. You can track this bug here: ID: 3275738 Kudos for your optimism I have added your post to the bug tracker, its in the system now, which is better than before
  7. Why not just use OpenG? RT @lavag: #labview 2011 feature: VI wrappers with error terminals for Wait (ms), Wait Until Next, & Tick Count

  8. You can track this new feature here: ID: 3275249
  9. Congrats to John Lokanis for passing his CLA! - well done mate!
  10. I guess the question I have here is that if a reuse library is tested and vetted code then why does it need DETT calls in it all time or is the dist version? (There may be a logical answer I am missing here). Anyways, I try and keep my reuse VIs lightly coupled. DETT is an add-on toolkit ($$) so sharing your VIs could be an issue however, if its company standard to have DETT always installed then this might not be a big deal internally. Cheers -JG
  11. So it seems the summary is to use a higher version if you can, but 8.2.1 is better than 8.2 Also, here is the versions to use that relate to your original questions: - dynamic dispatch recursion (as in reentrant dynamic VIs - LabVIEW 8.5) - properties (as in property nodes - LabVIEW 2010) - friends and community scope (LabVIEW 2009)
  12. Well, this is just an example template I use for teaching taken from NI Intermediate 1. Thought it may help in this case to describe exactly what you were talking about (using user event to communicate and error from consumer to producer). Cheers -JG
  13. Good points. It wasn't until LV2009 that the AB had a makeover and due to a new internal file/folder layout, file collisions do not occur and are not stored outside of the EXE (looks real messy for clients). Now I may be smoking crack here, but I was under the impression that you couldn't built an EXE that contained LVOOP in 8.2 due to a number of issues (may it was certain features?) - you have to use 8.2.1? I tried googling and found this. Of course AQ would know best.
  14. Hey... ...that's confidence! I am sure you will be fine, the exam feels harder than it is to pass IMHO. I prepared by having a game plan, I mean if you are designing and coding as part of your job, you should be getting all the practice you need, right (except for the fact you don't have access to your tools, templates and reuse code etc...)? I had a chat to Omar before taking the exam and he summed it up best for me: Quite simply, start at a high level and get the framework down, then iterate over it as many times as you can adding detail (code or requirements) keeping in mind you don't have to code it - that's not the point of the exam. So I pretty much followed this top-down approach and it works well. Cheers -JG
  15. Taking history lessons from the great @crelfpersonal and @JustinGoeres.

  16. Crelf has proposed a minor update to the OpenG Comment in the OpenG String library.
  17. Hi sjukheter Here is another example using User Events to communicate based on the above discussions. Cheers -JG PC Events - LV85.zip Code is in LabVIEW 8.5
  18. Yes, if memory serves correctly, 8.2.1 was a massive upgrade for LVOOP rather than the standard minor fixes. Anyways, I have seen weird stuff with using it so I wouldn't recommend it (I was forced to by a client's license). Of course it makes sense that the standard features are more stable in the latest LabVIEW versions (and that there are more features as well). IMHO I would recommend LV2009.SP1 if you have access to it - lots of features and really stable. Of course it comes down to your requirements and resources etc...
×
×
  • Create New...

Important Information

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