Ton Plomp

Name: Align and distribute Submitter: Ton Plomp Submitted: 05 Dec 2010 File Updated: 23 Jan 2011 Category: General LabVIEW Version: 2009 License Type: BSD (Most common) Align Distribute objects v1.2.0 Copyright © 2010, Ton Plomp All rights reserved. Author: Ton Plomp LAVA Name: Ton Plomp Contact Info: Contact via PM on lavag.org LabVIEW Versions: LabVIEW 2009 and up Dependencies: No dependencies, demo VI needs the OpenG time library Description: A set of VIs to align or distribute a set of points or objects, they behave similar to the align and distribute functions in the LabVIEW IDE. These tools are usefull when dealing with objects that needs to be rearranged. The set of VIs is bundled in one polymorphic VI (align_distribute.vi) that has the following tree layout -Align -Top -point -rectangle -Left -point -rectangle -Bottom -point -rectangle -Right -point -rectangle -Vertical center -point -rectangle -Horizontal center -point -rectangle -Vertical center -point -rectangle -Distribute -Top -Left -Bottom -Right -Vertical Centers -Vertical Gaps -Vertical Compress -Horizontal Centers -Horizontal Gaps -Horizontal Compress Installation and instructions: Use the VI whereever you want, or install it into your user.lib with VI Package manage (http://www.jki-soft.com/vipm) Examples: The zip-file includes one DemoVI that moves front panel controls around Known Issues: Acknowledgements: Icons are supplied by National Instruments in the LabVIEW IDE Version History: AlignDistribute - 1.2.0 (Released 2010-06-28) ============================================= - 0000021: [bug] The palette shows Align Distribute.vi as name. v1.1.0: Initial public release of the code. License: This code licensed under the BSD license ==============Start of license================== Copyright © 2010, Ton Plomp 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. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the . 4. Neither the name of the 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 ''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 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. ==============End of license================== 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 "Distribute objects" support page. Distribution: This code was downloaded from the LAVA Code Repository found at lavag.org Click here to download this file

I use the license of my employer at home. However every once a year I look into buying one myself (preferable a used license) or a debug license which are cheaper. My employer is not interested in the code I produce at home, nor has the intention of ever selling code themself, my contract was just 2 pages. Our IT-rules say that I can install a local copy of MS Office for instance, and they don't make a note that they have the IP on the documents I write with MS Office, I extrapolate this guideline into a field of interest. (on the same basis I use Total Commander at home, which would be the second piece of software I would buy when starting my own company). Ton

Have you changed any of the default font-style (specific the front panel default). Ton

Yair is correct, working on Password protected BDs is kinda difficult. For instance what should happen with the block diagram after capturing? Should it lock? There is some code for that purpose, but I think it's removed from the current stable revision. Ton

No updates on this. The chatter I read about the Twitter implementation of OAuth is kinda 'discussable'. I would love to have a generic OAuth toolkit that could work with Twitter. Ton

First step would be to XOR the old and new array. Then using a 'Not Equal to 0' node, you will get a boolean array where true means 'changed'. Then you need to check how much elements are true. You could convert it into a 0, 1 intger array, and use the sum of the array to get the number of changed elements. Ton

That is normal, VIs are enclosed in there own application space. If you want to open a (global) VI in a different application/project, you need to open a reference to that application first. Ton

Sorry, I meant, removed compiled code from VIs. Darn..., to be clear the VIs posted at bitbucket should have the blockdiagrams present! The world of SCC now gives me the power to get the latest version -1, remove the compiled code and recheck in. EDIT:And if I really had removed the code, you could always get a version earlier. Ton

Sorry for the late reply (I really want an up to date RSS-feed). Here I have posted some VIs that are meant to calculate hashes and keyed hashes. Ton

Pretty good. I am still working on a Mercurial API, together with a Source Control Provider. (I think I finished it almost) One of the best things is that it's quite easy to set up a public mirror of your repo's. For instance when I develop a tool, I normally push to my private server, but once every release I push to my private server and to a public server where people can get a clone of the history. Your right that the size of a LabVIEW repo is substantial (there is no compression possible in the latest LabVIEW versions) and every changed VI is stored as is. Ton

I'm not sure what you mean by phase, but in my book that's exactly the same as the starting angle. If you have for instance a starting angle of 90 degress, you will get a cosine wave instead of a sine. Ton

Could we have a Singular to Array in type conversion? A simple 'Build Array' will do. Ton

Hi Chris, somehow the FP.NativeWindow property with the OS handle to the Front panel window is not available in the official release. i always have to dig up some old version to code it. Ton

Perhaps the 'VI will be purged' event is something you want? Ton

You can use LabVIEW Profressional (not Base or Full) together with PushOK SVNSCC plugin. It's rather cheap (€30). Or JKIs TSVN interface which connects to SVN via TortoiseSVN. Yes, please specify, you might need to uncheck the 'tread read-only files as locked' option. Also explore the 'Source Only' setting if you are using LabVIEW 2010. Ton

They (tips and tricks) are aggregated on the LabVIEW Wiki. Ton

Ome Henk, another fine example from the dutch music industry (along with 2 Unlimited), he used to be targeted at 10 year olds, I assume he just follows the aging of the same people. No, it's definitly not Jamie. Or is it that small rear-shot you mean? Ton

The Webservice escapes it's response so it's easy to parse (and you cannot interfere between data and communication layer. You can use RegExes to find the Value and unescapes it to use it with XML functions: Ton

The Code Capture Tool 2.1.2 has the option to back-save the snippet in an earlier version. Download it here (LAVA) or here (SourceForge). Ton

Here's a is a limited API for TDMS in Linux, mac and RT. Ton

LabVIEW offers a built in option to create snippets. It's a very inflexible method to create snippets. But I am working on the CCT functionality for this feature. Ton

Allright I voted, however I think that NI should not only implement the easy ideas from the Idea Exchange. Basically all the ideas implemented are 'low hanging fruit', I would be ashamed to name those new 'changes' as the major upgrade feature (as NI is currently doing). Ton

One thing to remember are the 'arrow up ' and 'arrow down' keys. (oops, you didn't tell your users. Now they know.) I always try to be the first time when a new user / program is activated. The human brain is very inventive how to solve an issue. Source Ton