Leaderboard

Name: Scripting Sandbox (RCF Plugin) Submitter: vugie Submitted: 06 Dec 2010 File Updated: 03 Jan 2011 Category: VI Scripting LabVIEW Version: 8.2 License Type: BSD (Most common) Scripting Sandbox RCF Plugin Copyright © 20010, Wojciech Golebiowski (vugie) All rights reserved. Author: Wojciech Golebiowski (w_golebiowski (at) tlen [dot] pl) Name: Scripting Sandbox Type: Right Click Framework Plugin LabVIEW version: 8.2 Description Scripting Sandbox is a simple Right-Click-Framework plugin for quick creating and using of flexible scripting VI's without implementing additional RCF plugin. In other words it's a plugin for making plugins which you don't want to distribute, but rather to use internally for work automation in quick and dirty way without any error handling etc. You simply define a directory for storing so called SandScript VIs. RCF menu is being updated according to the content of this directory. SandScript VI has to follow provided template. When you invoke certain script, RCF simply passes whole current "Active VI" cluster to it (VI state, panel and diagram references, array with selected objects and mouse position) Installation Preferably use VIP package and VI Package Manager. Alternatively download ZIP, extract to \resource\JKI\RCF\Plugins\ and restart RCF Examples Few example SandScript VIs are included in Scripts subdirectory. To see them working, copy them to your scripts directory (defined within RCF plugin options) Support If you have any problems with this code or want to suggest features: please go to lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "Scripting Sandbox" support page. Version History 1.0.0: Initial release of the code. 1.0.0.3: Not savable SandScript VI bug fixed 1.0.0.4: Some docs updated License (BSD) Copyright © 2010 Wojciech Golebiowski All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. 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. 3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 AUTHOR 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

I'm with Daklu here except that if you're using the waveform type this isn't quite true - you can add anything you want to the waveform as a waveform attribute (metadata) and LabVIEW still treats it as a waveform data type and the queue is still valid. Mark

I reproduced this behavior. It seems that you use ClearType font smoothing. So there are gray levels in the image. Just modify the code in such way: You can change font smoothing setting in Windows with Screen properties->Apperance tab -> Effects button -> Smoothing method->Standard (sorry, controls names may not be exact, because I translated them from localized system version). BTW - it seems that Get Image method does not exist in 8.2 for anything but diagrams. If you want to make the code general, you should use Get Image of Block Diagram instead and trim it with Master Rectangle of structure

You should be able to get 1 bit Image Depth as well, wire the constant value 1 to the Get Image Invoke node's Image Depth input. Maybe your Unflatten Pixmap screws up the image. //Mikael

I have a student version of LabVIEW 2009 for my kids (home school).