Jeffrey Habets

VITech will bring along this uniquely boxed Raspberry Pi. 😊 Completely ready to run LabVIEW programs out of the box.

Great to see the LabVIEW wiki alive and kicking again!

Hope to have a bit of time to contribute sometime after NIWeek...

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

I don't have the link, but I remember someone else telling me that you can choose the INI file to use, in a command line switch.  This forces LabVIEW.exe to use a different INI file somewhere else on disk.  You could have a batch file that launches LabVIEW.exe with an alternate INI this way too.  I've never tried this so sorry if this is incorrect information.

http://www.labviewwiki.org/Custom_LabVIEW_configuration_file

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!

It was just around dinner time here, so unfortunately I missed it.

Going to watch it now!

I just want to confirm that I'm also unable to see the RSS feeds in Firefox for 1 or 2 weeks now.

You know, if you programmed graphically it wouldn't hurt so much.

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.

By the way, if you're reading this thread and don't know what the GDS is, have a look at it here. Then download and install it. Do it. Do it. Install it. Do it.

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. )

What a coincidence I might just happen to, by pure chance, pass on your contact info, but it's going to take another month until the guy in charge of the project is back here. So don't hold your breath

I won't.. I'll keep on breathing.. Hot Texan air for the coming week.

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..

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.

I'm in too... Just bought my ticket.

This did it for me.

My flight out of Austin is Friday 4.00pm so I'll be hanging around some on Friday.

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.

Congrats! Enjoy the time to come helping the Hello World code grow to an efficient concurrent framework!

Now if only you could hide it at runtime, or make it 0 pixels in size.

Absolutely! I'd kudo it, but I already did when the Idea was submitted a long time ago.

I also have to resize this decoration on a panel size, to ensure it's always surrounding the combo box at exactly the right size.

This can actually be achieved without doing any coding in the panel size event. Just need to have the correct correct combination and usage of a splitter bar, grouping (the combo-box and decoration) and 'Scale object with pane' and you can mimic the behaviour QD window without coding. Set pane sizing for all panes to 'Scale objects while sizing' and it even gets better!

Programming UIs in LabVIEW is fun!

Absolutely! And it got a whole lot better since the introduction of splitter bars!

I just landed. I'll have a car. I'll leave from the hotel around 7pm. Let me know if you want to meet in the lobby

Cool, that would be great!

Imagine me with black glasses and you'll probably recognise me.

Congratulations!

I will be there too.

Is there anyone carpooling from the hotel?

I'd be interested in catching a ride with someone too.. Seems quite a walk according to Google maps.

I arrive Saturday night.. So count me in!

Free food is my favourite dish.

I've booked flight and hotel two weeks ago, so I will be there in Austin!

I've been using OpenG for a long time and will keep on doing so. It is standard in our pallets! If I need to work on a customer's system without it, first thing I do is install VIPM & OpenG.

I do the loading of a class from one of the methods, basically I 'construct' the class from file. So I have e.g. a Load method for constructing a class+data from a file and a New method for constructing it without data (or whatever the New method needs to do to initialize the data, which in my case is nothing). Since the class' load method is called, it will for sure be present in the exe, as well as the classes it aggregates (Channel in my case). Works fine here.

Yup!

Perfectly legit way of working if you ask me.. You need to write the code anyway, so why not use it to do the 'checking'. It saves you the work of writing the extra code to check what the exact format of the path is.

As Mike, I most often use this construct too when attempting to connect to certain instruments.