Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/20/2012 in all areas

  1. I think it's possible in any version. I did a quick test and it looks like you should be able to call resource\Framework\Providers\VILibrary\LIBUIP_Properties_Dialog.vi with a reference to the new class then it will do exactly what you want. You just need to invoke Save after the dialog closes.
    2 points
  2. Howdy Attached is a tool that automates the creation of a Child Class in the LabVIEW Project Environment. This is my first foray into LabVIEW Project Integration, and was a good example as it is a simple one. There are no example VIs in package yet, but here is a video: <!-- copy and paste. Modify height and width if desired. --> <object id="scPlayer" width="470" height="625" type="application/x-shockwave-flash" data="http://content.screencast.com/users/jgcode/folders/LVOOP%20Assistant/media/2d60299d-20fc-47df-ae5d-da3987577dc2/jingswfplayer.swf" > <param name="movie" value="http://content.screencast.com/users/jgcode/folders/LVOOP%20Assistant/media/2d60299d-20fc-47df-ae5d-da3987577dc2/jingswfplayer.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/jgcode/folders/LVOOP%20Assistant/media/2d60299d-20fc-47df-ae5d-da3987577dc2/FirstFrame.jpg&containerwidth=470&containerheight=625&content=http://content.screencast.com/users/jgcode/folders/LVOOP%20Assistant/media/2d60299d-20fc-47df-ae5d-da3987577dc2/LVOOP%20Assistant%20-%20Create%20Child%20Class.swf&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/jgcode/folders/LVOOP%20Assistant/media/2d60299d-20fc-47df-ae5d-da3987577dc2/" /> Unable to display content. Adobe Flash is required.</object> For things like this - Project Integration has a more natural workflow than '>>Tools' The package is LAVA namespaced as I plan to release this on LVTN and also to release more LVOOP helper tools. Feedback welcomed! lava_rsc_create_child_class-1.0.0.14.vip
    1 point
  3. Here are the VIs after some work on icons and adding an additional function to return the fully-qualified class name. I’ve made the smaller VIs “inline”. I also changed “Get Default Object” to being based on “Preserve Runtime Class” as I found that the zero-iteration method sometimes didn’t work when in an inline VI (some detail of the complier that I don’t understand). PS to jgcode> what is the next step in possibly getting these into OpenG? OpenG Suggestions.zip
    1 point
  4. Hi, I'm a LabVIEW coder of about three years. I've never had the opportunity to take the CLAD or CLD exam, but I'm approximately between the two in skill level, based on what I've seen from the practice tests, etc. I'd really like to get involved in open source LabVIEW work, but don't really have too much opportunity at my new job. I'd really like to strengthen my LabVIEW chops and this seems like as good an avenue as any. Can I contribute to OpenG, or some other open-source LabVIEW project? If so, how can I get started? Please forgive me if this has all been answered already elsewhere. Cheers, Randy
    1 point
  5. Hello Randy, you're more than welcome to participate with OpenG. Currently Jonathaon Green is the lead developer of OpenG, so you can send him a direct message if you want some 'tasks'. For instance you could have a look at the bugs posted at sourceforge, and see if you can tackle them (I advise you to take a SF account in the process as well). Another way to participate is to go over the proposals in the OpenG forum, and give your opinion, try to find weak spots or improvements. If you have code you feel is general enough you can add that to the proposal forums as well! Ton
    1 point
  6. Cross-posted here - http://forums.ni.com/t5/LabVIEW/Database-Errors-after-switching-to-MS-SQL-Express-Database/m-p/1844547/message-uid/1844547#U1844547 I'm with asbo - search for the exceptions online. Also, you could try wrapping your DB actions in non-reentrant VIs, so that they don't execute in parallel, but that's just a broad statement.
    1 point
  7. I'm pretty sure you can hook into the New... menu and can control where in the project item is added. Is there a reason you didn't add the item to the New... menu? That's where I would expect to find it. (I know that everything in the New... menu is added to the project item that is selected and this would be different. But that's still where I would expect to find this.)
    1 point
  8. A very fine tutorial manual exists within LV's help files. Launch LabVIEW. On the Getting Started Window, in the right hand column, click on the link for "LabVIEW Fundamentals". This launches the LV help. In the left hand column is a list of topics. Search for "LabVIEW Object-Oriented Programming". The first link you'll find is for "LabVIEW Object-Oriented Programming error codes". Keep searching. The second one is for "LabVIEW Object-Oriented Programming". That's the link you want. Underneath that topic is a whole range of Concepts and How-To articles. If you printed it on paper, it is almost 70 pages of really good information.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.