Leaderboard

Name: UI Tools addon: Tree & Tagging Submitter: François Normandin Submitted: 10 Jan 2010 File Updated: 16 Feb 2010 Category: User Interface Version: 1.0.4 LabVIEW Version: 8.6 License Type: BSD (Most common) UI Tools Tree OOP Add-On v1.0.4 Copyright © 2009-2010, François Normandin All rights reserved. Author:François Normandin Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 8.6 Dependencies: lava_lib_ui_tools >=1.0.36 Description: This package contains classes for manipulating Trees with some enhanced features. It consists of a set of VIs to create tree objects and associating tags with data in a variant format. Includes: - includes some icons from FamFamFam (see license in _Symbols directory) for demo purposes. You do not need these icons if you use the Tree OOP classes in your work. Instructions: After installing package with VIPM, refresh palettes if VIPM is not set to refresh automatically. You will find the palettes in the UI Tools functions palette (user.lib) Known Issues: - No drag and drop functionalities included. You'll have to do that on your own if wanted. (for now anyway) - Arrays will be shown has a succession of Unnamed items. Recursive VI provides a way to put it on a single line within brackets, but has been removed to provide backward compatibility to 8.6. An add-on will be posted for LV 9.0+ users. - The Children & Parents Symbols synchronization works only for Symbol indexes 1-2-3 (True-False-Mixed). - When adding an item on the same level as an existing one, it gets added in front. Expected behavior would be to have it added afterwards. - Modifying a child's data does not recursively modify the parents' data (cluster variants). This will become obvious once you try the framework... This functionality will be kept in my mind for future improvements. Acknowledgements: Norm Kirchner from which I got some tricks in his Tree API (see LAVAG.ORG) Change Log: v1.0.4: Solved problems with hardcoded path for symbols installation. Affected primarily installations on 32-bit Windows systems. v1.0.3: Initial release of the code. (LV 8.6) License: Distributed under the BSD license. Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to the discussion page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org ============================ Click here to download this file

Name: GetSnippet Submitter: jcarmody Submitted: 23 Dec 2009 File Updated: 03 Jan 2011 Category: *Uncertified* LabVIEW Version: 8.2 License Type: BSD (Most common) GetSnippet RCF Plugin v1.0.0 Copyright @ 2009, Jim Carmody All rights reserved. Author: Jim Carmody LAVA name: jcarmody Contact Info: Contact via PM on www.lavag.org LabVIEW version: Created and tested with LabVIEW 8.2 Dependencies: JKI Right-Click Framework LabVIEW 8.2 or higher Description: The Code Capture Tool 2.0 can create a VI snippet in LV versions as old as 7.0; this plugin lets you extract them in versions 8.2 and above. Standard conditions apply - you won't be able to extract a snippet that was created in a newer version of LabVIEW. Instructions: Extract the zip file into [LabVIEW]\Resource\JKI\RCF\Plugins\GetSnippet and restart the RCF framework. Once installed, select a snippet, activate the RCF and select GetSnippet and your decoration will be replaced by the underlying code. Known Issues: Hardly anybody makes snippets in anything except LabVIEW 2009. The program works fine, though. Acknowledgements: Ton Plomp and Yair gave us the Code Capture Tool, without which there would be no need to extract snippets in LabVIEW < 2009. Darin.K showed me how to get a VI from a snippet. Ton helped me improve my implementation. Change Log: v1.0.0: Initial release of the code. License: BSD Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "Abort.vi" support page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org Click here to download this file

Check the date of this story. I'm too old NOT to remember. You youthful but ignorant and arrogant "whipper snappers".

In vi.lib\Utility\tcp.llb there's a VI called TCP Get Raw Net Object that will return the current socket handle. You could then use the socket handle as an argument into a CLN call into a DLL that could then call the Winsock DLL (assuming you're on Windows) and set the TIME_WAIT value... I think... I haven't done it. Or you could just ask yourself if you really need to reuse the same client side port or just let the client grab the next available one to reconnect to the server. This would be a lot easier. Also, are you sure the handshaking with the server is happening exactly the way you think it is? Have you looked at the transaction with a port sniffer like Wireshark? Mark