Leaderboard

When working with code that uses LVOOP property nodes, debugging becomes difficult because there is no easy way to go to the accessor code that runs when the property node executes. So in order to alleviate this I created the Property Popper. Run this floater helper VI (leave running during development) When you want to get to an accessor, select the property node Click 'Get Properties' on Pop Property.vi Double click on the property you want to get accessor access to Enjoy ~,~ The Captain was here See Video Detailing this <!-- copy and paste. Modify height and width if desired. --> <object id="scPlayer" width="892" height="708" type="application/x-shockwave-flash" data="http://content.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/jingh264player.swf" > <param name="movie" value="http://content.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/jingh264player.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/FirstFrame.jpg&containerwidth=892&containerheight=708&content=http://content.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/2012-01-10_1033.mp4&blurover=false" /> <param name="allowFullScreen" value="true" /> <param name="scale" value="showall" /> <param name="allowScriptAccess" value="always" /> <param name="base" value="http://content.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/" /> <iframe type="text/html" frameborder="0" scrolling="no" style="overflow:hidden;" src="http://www.screencast.com/users/NJKirchner/folders/Jing/media/e7471e93-bf0b-4801-b050-8e7c58d7a0fc/embed" height="708" width="892" ></iframe> </object> pop property.vi

I don't 100% follow the above (I think our definitions of things are different - but that's ok). If it helps here are my posts in summary: I agree with using FGV/MFVI/AE's etc... on a module per module basis I think all approaches discussed are valid - there are good reasons for both (I particularly find ShaunR's perspective in his last post above very interesting) I just personally prefer creating an API for a module I really like the 'LV2009' approach and hence wanted to post it in this thread to share with the OP

I was able to answer this question regarding if CC licenses were suitable for LabVIEW code when I was researching for another thread. From Creative Commons website: Good to know