Francois Normandin

Definitely plausible. I think it's clear it's a situation to avoid, but just for the sake of understanding, why would there be a difference between in-project and out-of-project VIT?

Honestly, this is the first time I use a VIT file for instantiating VIs. (Probably first time I save a VIT file altogether!) I naively thought I'd put my "template" in the Getting Started Window where I could call it with other templates... Isn't that what templates are all about? Of course I'll put this VI has a "Drop VI Content" icon in the palette and will never use the GSW template... but that's not the point. I had a perfectly working VI and when I saved it to a VIT file, I tested it one more time before packaging it and noticed it was slow on first generation calls. And by slow, I mean 3300ms! (200ms for the stripped down VI I posted above). Copying an entire 184kb VI in memory should not take 3.3 seconds. If there is something potentially going wrong under the hood, I think it's my responsability to point it out for further investigation by the experts. Then again, it might be perfectly normal. I would not even have noticed a 200ms delay in launching the async VIs. And frankly, I never heard of anything like "don't use VIT files anymore, they're useless". If it is an official message, then it hasn't been heard.

Yep, I confirm this too on my machine. Well, this is mostly for understanding how it works under the hood, because a VIT file is not intended to run as a main program, unless in Development environment. It's gonna end up in a palette with "Drop VI Content"... I'll send a support ticket just to know if that's a bug or expected results like suggested by James. Looks like Crossrulz has the best computer after all.

He's still faster than on mine.

Thanks Shaun. Perhaps I should restart LabVIEW. Edit: I'm on LV2011 (no SP1) 32-bit.

I was updating a reuse template of mine for asynchronously calling itself to simulate as an example for inter-process communication tests. It took me some time to find out what was causing the first level to be slow. It seems the culprit is the reference to the VIT file. The stripped-down template below (LV2011) launches a clone of itself everytime we press the "Launch Async" button. Async Launch of VIT.vit You'll notice the time required to open the reference is immensely larger when you click on the first copy than on any others. And it scales rapidly with VI size. My full template is 184kB and takes 3.3s to load the reference. This one is 20kB and opens up in ~200ms. Simply changing the extension to .VI solved the problem. Is there anything I'm not doing correctly? Should this be considered a bug or a feature? Edit: Added a small video on Jing... http://screencast.com/t/aN29fYxJw3A6

I thought the VI was way too simple to upload, but hey, here it is . Reproduce Pane Background Property Bug.vi Edit: CAR # 347359

When there are multiple panes on a front panel, the pane background image will return the image of the previous pane when empty. EDIT: CAR NUMBER 347359

Done. Looks like it's been abused for close to 4 months. Since the site is not maintained anymore, I don't know if the admin can make the front page un-editable?

The native LabVIEW variant palette doesn't have a "Variant Constant". I personally find this one very useful.

Small modification to AQ's VI... Get the Value from the control associated with the terminal. Indeed, the datatype is always "LabVIEW Object" in this case. Get Name of Class of Object From Terminal Reference.vi (LV2011)

Congratulations Stephen and many thanks for your involvement in bringing OOP to LabVIEW. I can say that it changed a lot of things in my programming, all of them for the better. It's given me the opportunity to tackle problems in a whole new light and I feel I've improved both my pleasure and productivity while tackling them. I hope I can say the same again in 3-5 years.

NI has a set of wifi DAQs. Easy to deploy, reliable, same coding as any other NI modules. http://sine.ni.com/nips/cds/view/p/lang/en/nid/205686 If you don't have the budget for these nice modules, you could setup a bluetooth connection (115 200bps) to get enough bandwidth. http://arduino.cc/en/Main/ArduinoBoardBluetooth You'll need to feed the microcontroller with your analog data which means you'll need to create a shield with 2x 16-bit analog ADC chips. But the rest is just sending your stream of bits over Bluetooth to your computer.

As pointed out by Asbo, for an arbitrary length string array, you can't make it into a fixed-sized cluster.However, you could use variants to build a "Variant Cluster". If so, OpenG is your friend here. Furthermore, this works with any array type (see attached VI). ArbitraryArrayToCluster.vi (OpenG VIs needed -> VIPM)

I couldn't find the old code. That was prior to me learning to use SCC ;-) Here's something equivalent to what you're looking for. It's in LV2009. Launch the test VI to get an idea of the functions. WinError_class.zip (LV 2009)

I think it's not about the connector pane, but rather the small "ears" I added to the icon

How about this?

Unzip this file under the "LabVIEW Data\LAVA\Control Templates" directory and you'll get a Silver-looking template installed. Silver.zip Note that this button doesn't resize well, just like the other templates, because it creates a fixed-size image of all button states. I'll investigate how to programatically change decals, but that's not something you should expect soon. I have too many other things on my mind. You can also create your own templates and drop them in the same directory as stated above. SImply create three PNGs with the button backgrounds you wish and name them like the templates (templatename_1.png, templatename_2.png, templatename_3.png), then make sure that these pictures are "clipboard-copied" on the templatename.ctl different states. The rest is magic . edit: You should do the template in the lowest possible version, so that it can be called from whichever version you use...

This seems to be the same problem than UI Tools: Control addon. I'll check this and post a new version in VIP file format soon. Stay tuned. New version uploaded with corrected namespacing for the JKI State Machine dependency. Please report if this doesn't solve the problem. Note that this package gets installed in the new LAVA palette...

New version available for LV2009 and above. (v1.2.1.9)

You can download previous versions in the CR. Links are on the right side of the page. http://screencast.com/t/p6K4XBous Quick link: http://lavag.org/index.php?app=downloads&module=display&section=download&do=version_download&id=196

Hi Chris, Sorry for the late reply, I've been on vacation last week. This package is an opg file dating back to vipm 3. I had to deal with post-install and pre-uninstall VIs myself. I might have made a mistake in the code and there's a messing up during upgrading. When I downgraded to 1.0.15 in LV2010, I got the same problem you have. (missing jki files with uitools namespace) I downloaded 1.0.14 and downgraded it one more step and it worked. But I couldn't get version 1.0.15 or 1.1.0 working. It seems the error is also with the Bitman dependencies. I'll try and put up a package 1.2 in *.vip format. In the meantime, you can use 1.0.14. Let me know if that's a workable solution in the meantime.

I'd find more natural to find this in the MD5 palette.

Hi Bastian, just to make sure... this add-on doesn't give you access to Word and Excel reports without a purchased license from NI. It simply adds OpenOffice Writer to the list of choices in the Report Generation Palette. If you have a valid RGT for Word license and my add-on doesn't work in an executable, then it's something I'll investigate. There shouldn't be any links between the RGT for Word/Excel sold by NI and this piece of code, but the package does replace a single VI to select the right class (the one including ooWriter in the Enum). It has been done in LV2009, so perhaps something has changed in LV2011. Did you ever try the addon in an executable with LV2009 or 2010? (Is this a new issue with 2011?)