Barrie Posted November 2, 2006 Report Share Posted November 2, 2006 Hello All: Rather than use trial and error to find what the terminal indices are, (and to explore scripting) I wrote this little utility. Feel free to suggest any corrections or additions. Cheers, Barrie Oh, and thanks to Chris Davis for the "leg up" that got me this far. B. Download File:post-658-1162432064.llb Quote Link to comment
Mike Ashe Posted November 2, 2006 Report Share Posted November 2, 2006 Barrie, nice tool, but since you saved in a library you might want to save with options and include the specific OGTK VIs in the library. Some companies won't let us use the whole toolkit, but individual VIs are okay. Quote Link to comment
Barrie Posted November 2, 2006 Author Report Share Posted November 2, 2006 Barrie,nice tool, but since you saved in a library you might want to save with options and include the specific OGTK VIs in the library. Some companies won't let us use the whole toolkit, but individual VIs are okay. Gee, I thought everyone had the OGTK ! Good point actually. :thumbup: Here is the full .llb (with some diagram clean-up) Cheers, Barrie Download File:post-658-1162506452.llb Quote Link to comment
Chris Davis Posted November 3, 2006 Report Share Posted November 3, 2006 Gee, I thought everyone had the OGTK ! Good point actually. :thumbup: Here is the full .llb (with some diagram clean-up) Cheers, Barrie Barrie, I used the pic ring off of your example in a new code repository upload I did last night. Thanks, this tool is/was helpful, I've got an idea on how to use it in another example. Quote Link to comment
Mike Ashe Posted November 3, 2006 Report Share Posted November 3, 2006 Gee, I thought everyone had the OGTK ! Good point actually. :thumbup: Sadly, some large companies have a legal department that is afraid of getting sued if they use open source code. They are worried that someone will put proprietary code into the open source, then after it is distributed the owner of the code will find out and sue. Naturally the suer would never go ofter the little guy who put the code in, lawyers don't bother with that, they go after whomever they can who has the deepest pockets, ie, major corporations. Sad but true. Part of the reason for this is that most of the open source code that we would have available in LabVIEW is licensed under LGPL, which is overly long (what was it? 16 or so paragraph/clauses? ). There is a possibility of relicensing the OGTK using the BSD license, which is simple and lets end users do just about anything as long as they don't come back to sue the originals. Quote Link to comment
crelf Posted November 3, 2006 Report Share Posted November 3, 2006 There is a possibility of relicensing the OGTK using the BSD license... BSD = :thumbup: Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.