Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/09/2011 in all areas

  1. Name: OpenG Config XNodes Submitter: GregSands Submitted: 08 Jun 2011 File Updated: 08 Jun 2011 Category: *Uncertified* LabVIEW Version: 8.6 License Type: BSD (Most common) These XNodes wrap the OpenG Variant Config routines so that clusters are automagically returned as themselves rather than as variants. The XNodes simply call the OpenG routines, as I didn't want to have to worry about handling (or rewriting) the reentrant algorithm used. XNodes are provided for Read/Write INI Cluster, Read/Write Section Cluster, and Read/Write Key, and should work as direct replacements. Many thanks to Gavin Burnell for his extremely helpful toolkit, and his release of Array XNodes which provided the inspiration for trying my first XNodes. I also use a modified version of the XNode Manager by Aitor Solar to create the initial XNodes. All the usual caveats apply when using XNodes - i.e. don't, unless you know what you're doing, or don't care what happens! Dependencies: oglib_variantconfig >= 2.7-2 lava_lib_labview_api_scripting_tools >= 0.22.2.22 Click here to download this file
    1 point
  2. Unfortunatly NI is looking at XControls as second class citizens. I filed a bug because LabVIEW is ignoring .xctl files in user.lib during auto-indexing of the palettes, but this was rejected. My current work is: -Move the XControl and all of the sub-vis into an hidden directory (starting with an underscore '_') -Create a palette file next to the hidden directory that contains the actual XControl, and any other controls/VIs I want to expose Move those to files/folders into user.lib I posted anIdea on the Idea Exchange about this behaviour, that definitly needs more votes (currently 9 ), where JGcode mentions that he got a CAR (236395 ) Ton
    1 point
×
×
  • Create New...

Important Information

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