Leah's LabVIEW Blog

This is the final post about the MLUG Beer Money challenge: if you are lost, start here . The first solution method that I describe isn't particularly fast, but it is fun.

This is Part 2 of the beer money problem, see intro and Simple Nested Loops Solution (#1) . Recursion - yay. Having a VI that calls itself that calls itself that calls itself... then finally breaks out. 

This post is about my first attempt at answering the MLUG beer money challenge outlined in this post . So, where to start? After grappling with this problem for a while, I decided to type up exactly what I was doing when trying to solve it on paper, and go from there.

I like a good coding challenge, and this one is particularly fun. It was set by the wonderful folks at MLUG and goes like this: I went to the supermarket to get some beers for the Euros final and my bill came to £11.99. With the money detailed [below], how many combinations are there that make up the exact change to pay my bill?  

I was very shocked when I heard the news at work about NI binning NXG . NXG was announced back when I worked at NI and I still remember the excitement people had for a more modern LabVIEW - that "ooh" as they demo'd the zoom, those flashy web VIs. 

 Greetings LabVIEW nerds, It's been a while! I've been busy. You see, recently I've been working on a re-use library that has the potential to be used by any LabVIEW developer within the organisation who is in a manufacture or test role - in fact, it could be included in every jig. So considering the number of people who might use it, it's worth taking the time to make it nice and developer-friendly. I've spent many hours writing the documentation, unit tests, examples, etc. Even to the point that I did a re-write to remove all dependences. (I hadn't realised that different versions of OpenG would cause headaches for people, oops.) Something that I sought advice on was my folder structure for my library. I had always been on team ' Project Explorer structure mirrors the disk ', but when it came to where my Unit Tests, VI Tree, Examples etc. lived, I couldn't make my mind up. And moving them around isn't an easy task. Top tip: You can click on a ...

Virtual Machines has always sounded like an awesome idea for developing. No unexpected dependences sneaking in, a clean version of LabVIEW and drivers for each project, what's not to like? And no more poking through the dusty PC graveyard every time I want to test an installer.