eberaud

Thanks to both of you. I will have to print and frame this golden rule!

Coincidence, I'm actually facing a related issue right now. My application is compiled in 32-bit and runs nicely on both 32-bit and 64-bit machines. However one new plugin I created calls a 3rd-party dll which has been provided by the supplier in both 32-bit and 64-bit versions. My code was calling either one or the other, based on the OS bitness. But now I understand from what I read that a 32-bit application cannot call a 64-bit dll. So my question is: do you think there is a way to use the 32-bit dll on the 64-bit machine? Right now the dll lives in a sub-folder in C:\. Should I move it to ProgramFiles(x86)? (the application always lives on ProgramFiles(x86). Sorry to hijack the thread a little bit.

If you use the conditional structure with TARGET_BITNESS, the selection happens at compile time. Now you need 2 computers: one to build the 32 bit version and one to build the 64 bit version. Wouldn't it make more sense to use a case structure and detect the bitness of the PC on which the application is being executed? To do that, I use the tip given by rolfk in this thread: https://lavag.org/topic/14002-determine-32-or-64bit-os-windows/

Thanks Crossrulz this is a very thorough article! Everybody else, I'm still eager to get more advice on error handling.

Dear all, I successfully passed my CLD just a few weeks ago at NIWeek and will attempt the CLA on September 10th. I did a lot of research, attended the session on the CLA preparation, and won't bother you with the usual basic questions, I think I have a good understanding of what is expected. However, there are two things I'd like your help with: 1) Requirement tag: I never used them and I'm amazed by how little information there is online. Where do you put them: - BD: Free labels, wire labels - FB: Free labels, free labels inside a cluster - Documentation inside VI Properties - Others? 2) Error Handling: I must admit I lack experience and knowledge about how to create an error handling module, let alone a good one! In my past projects, each module and sub-module was always performing its own error handling... Could you point me to a few different techniques and examples? I'd like to get a good understanding of what is expected from such a module. If I only look at the one from the sample exam, I'm afraid I will just try to memorize and recreate it and it's not what I want to do... I'll start working on the sample exams and will likely post my solution here to ask for some feedback. Thanks

I'm not a fan of using queues to wrap a DVR, since the whole point of DVR is to have an efficient way to read-modify-write a value in memory while guaranteeing its integrity. We make heavy use of DVR and it works like a charm now. During the development phase though, we did run in deadlocks and it's true that a timeout would have made our lives better. But I don't think the final architecture should use DVR timeouts as part of the design. They should only be here to signal an error and be treated as such.

Well it's not only the name. It does look like a wire, and like you said even reference wires obey data flow...

I'm on the same page as Shaun. Maybe it's a matter of habit, but for those of us who have been developing in LabVIEW for years, a wire always controls data flow and execution. This is a golden rule that suddenly doesn't apply anymore, and that's quite disturbing I find.

OK are those really 2 different pictures? Or did they just photoshopped the shirt?

Sorry but I just can't figure out what the picture represents on the 'receiver' side

I've been biking for a little while now and I finally joined the club!

That's only for accessing it through a web browser. What I would like is to use a FTP client like Filezilla. So I was wondering if there is a way to do that with a host, a user name and password, a port number, and so on...

What are the FTP info to access it through a FTP client?

As usual thank you Mark!

InnoSetup is free and awesome, I highly recommend it!

Makes total sense. Thank you Mark no matter what! I'm also planning to pass my CLD, so I need to remove even more sessions in my list, tricky tricky tricky...

I'll be at NI Week but obviously can't attend all the sessions I'd like to attend. Do you already know which sessions you are going to record? That way I guess I can attend the ones you don't record and watch the other ones after the NI Week. Is that a wise strategy? Thanks!

I use the SSS so rarely that I didn't even know it was directly on the palette in previous versions

What? It is still supported in LV2014. What version of LabVIEW are you using?

Just an idea: do you really need the LVFileRefs object? I feel like in your situation I would have put all the fields (path, refnum,...) in the LVFile object directly. Then each child object can have both the fields of the child class, and the fields of the parent class (LVFile). Obvisously you have spent much more time thinking of this specific situation than I did so my comments might miss the target, I guess I'm trying to brainstorm some ideas here

It looks like you need a Factory pattern. As soon as you know the type, create the proper child, it seems to me that you don't need to store the type as an enum anywhere.

Beautiful! Thanks for sharing.

Well if it happens again I'll talk to my IT guy! (that's my work laptop, not my personal one)

Wow while troubleshooting some code I noticed that calling the "Generate occurrence" function always returns the same reference if used in a loop or in a SubVI that you call several times. The only way to get different references is to physically place several instances of it on the BD. Is that the expected behavior? And in a more general way, what do you think of occurrences? I like them because they are so light and simple. I use them when I only have one "sender" and one "consumer" and that I don't need to pass any data... Edit: A glance at the LabVIEW Help indicated that indeed this is the normal behavior. I'm still interested in knowing what are your thoughts on occurrences...

I'm coming to NI Week and LAVA BBQ for the 1st time!