Leaderboard

Maintainable code is not really quantifiable-it is a subjective assessment. All code is maintainable, it's just how much effort it requires. Even a re-factor (euphemism for a re-write) is a form of maintenance. Good coding practice and style can go along way towards making the life of a programmer easier but, the crux of the matter is that it can look as pretty as you like and you could have filled out every description and hint but if it doesn't work; you won;t get paid and you won't be asked to come back. . Therefore it cannot form the basis of a performance or coding metric for the purpose of quotation or deliverable. It's a bit like "future-proofing" in that sense. Additionally, only programmers care about neatness because they are the ones that will be required to maintain it. A project manager just wants it to work and it's your (my) job to make sure it does even if the wires are out by a pixel or two. So I like the grading scheme here because it will be a good indicator that they can write working code under time pressure (like the day before delivery ).. programmer [proh-gram-er] : noun 1.a person who converts caffeine into computer programs.

I am sure that a lot of you already knew what the "add property" button does in the installer build specification, but I am so happy about this discovery and I couldn't find anything online that I decided to share my excitement with my friends in LAVA. The application I am building works with a third party software that requires my installer to add things to the %appdata% folder, in Windows 8 this translates to C:Users<username>AppDataRoaming The default destinations available in the installer build specification in LabVIEW includes the [Public App Data] but in Windows 8 that points to C:ProgramData The help says that clicking on the Add property button under the Destination View lets you add a new MSI property to the Destination View tree. You can find a list of MSI properties here: http://msdn.microsoft.com/en-us/library/aa370905.aspx#component_location_properties and in particular there is one called AppDataFolder http://msdn.microsoft.com/en-us/library/aa367565(v=vs.85).aspx Well, adding the new property AppDataFolder was enough to set the destination for my ThirdPartyApp and the installer now successfully installs files in %appdata% folder. I hope this helps others in search of this information. Regards, Fab

I didn't know about this, but haven't had a need to yet. Also XBMC Plugins? You must be doing some cool stuff.

Door prize: Four copies of a brand spanking new poster from National Instruments featuring code-artwork from yours truly.

I needed this for a project a while back...in my case, it was an array of pictures with zero borders (and no array element borders either). Here's a VI containing the array of borderless pictures, saved in LabVIEW 2013. Array of borderless pictures.vi

The big benefit for developers that I see here is that it may highlight some of the source control issues that we have suffered for many years. It may prompt changes in the core so that we can use these powerful tools (like github) much more effectively. I dare say that once you have 20 branches all pushing their changes, the nightmare of merging, cross-linking and phantom recompiles might be laid to rest once and for all That alone should be enough of an incentive to participate, if only because pushing changes will cause such havoc for the people merging the Master that they have to do something before they tear [the rest of] their hair out

Mike, not sure if this will help you, but if you add NI_Appbuilder_logging=TRUE to your LabVIEW.ini file then you will get a comprehensive build log for your .exes and installers. If your installer is failing to build just scroll down to the last line and see if there is a more verbose error message there. The log file is in the same directory as the .lvproj