Leaderboard

Name: Swap Terminals RCF Plugin 1.0.2-8 Submitter: gb119 Submitted: 04 Mar 2010 File Updated: 23 Aug 2010 Category: JKI Right-Click Framework Plugins Version: 1.0.2 LabVIEW Version: 8.6 License Type: BSD (Most common) Swap Termianls RCF Plugin - 1.0.1-7 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Copyright © 2010, Gavin Burnell All rights reserved. Author: Gavin Burnell G.Burnell@leeds.ac.uk"]G.Burnell@leeds.ac.uk[/email]"]G.Burnell@leeds.ac.uk"]G.Burnell@leeds.ac.uk[/email][/email] Distribution: This code was downloaded from the LAVA Code Repository: http://lavag.org/ind...p?app=downloads Description: This is a plugin for the JKI Right Click Framework (version 1.0.2). Ever inserted a primitive like add, subtract, greater than, or less than into a wire and manage to get LabVIEW to wire up the 'wrong' input because you right clicked one pixel the wrong side of the wire ? Ever looked at code and realised that you've got the input terminals hooked up the wrong way round on a select ? Then this plugin is for you, simply select the block diagram primitive, activate the JKI RCF plugins and select 'Swap Terminals'. This plugin will work on any primitve function or 'growable' function that has two and only two inputs and also on the 'Select' and 'In Range and Co-erce' nodes to swap the top and bottom inputs over and rewire the wires. In version 1.1 it will also handle 'Bundle' and 'Bundle by Name' which have two input elements and a special case of two wires that are wired into different terminals of the same node. Dependancies: JKI Tools Right Click Framework >=1.0.2 Support: If you have any problems with this code or want to suggest features: Change Log: 1.0.2-8 Corrected a regression in previous version with bundle/bundle by name nodes. 1.0.1-7 Rereleased as a VIPM Package File built using VIPM 2010. Should have correct package dependencies for RCF Packages 1.0.1.1 Added growable functions with special cases for bundlers and two-wires-to-the-same-node. Refactored the code to kake extending it for other GObject types easier in the future. 1.0.0.1 Initial release on LavaG License: Copyright © 2010 Gavin Burnell All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of Leeds nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Click here to download this file

Here is a LabVIEW 7.0 VI that you can use to programmatically determine the VI execution state settings for a specific VI. VI Exec Options.vi (LV 7.0)

Why don't you just open the VI and have a look in its properties dialog? Also, note that since it includes a write, it probably only matters if it's reentrant if you're working on two different objects at the same time, as presumably the framework will lock the cluster if you're working on a single instance.

I've been to a few brainstorming meetings that used some kind of Mind Map software. It seemed like a solution looking for a problem to me. I prefer good ol' whiteboards and notetaking. -D

As an aside, I prefer to disable and gray controls rather than hiding them. Or, if you must hide them, put them on a admin page of a tab control and the switch pages depending on who is logged on.