Jump to content

Ton Plomp

Members
  • Posts

    1,991
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by Ton Plomp

  1. If I want to embed an image from the NI forums (eg: http://forums.ni.com/t5/image/serverpage/image-id/15119iC34E97684EA14EAC/image-size/original?v=mpbl-1&px=-1) with the 'img' tag, I get an error upon saving the post stating 'You are not allowed to use that image extension on this board.' Could an exception be made for either the ni.forums or just ditch extension checking (allright, just ditch .bmp files) Ton
  2. Yes you can manipulate an event refnum: using a Cluster Bundle function allows you to wire two event refs into 1. Ton
  3. I have created a LabVIEW wiki page with this knowledge. Ton
  4. This sounds very interesting, but I agree with Yair, try to get in contact with Tomi Maila, who has written several OpenG Class templates, how do these two match up? Or am I totally missing your point? I would love to contribute, but I doubt I will have the time to provide quality code. However keep us posted. A good documentation resource would be the LabVIEW wiki. Ton
  5. Mark have you tried to run this tool with the JKI RCF framework active? I have a feeling that the 'VI Activation event' is not triggered in your app. Ton
  6. I think I know what the issue was with GIT Diff. I stumbled upon the same issues with Mercurial where the remote file was copied into the system temp directory. The LVDiff utility from Sourceforge tries to load both VIs in the same app.space. I edited the diff VI to rename the file in the temp directory. Some more details are on the Mercurial wiki page. Ton
  7. Francois, how did you manage to break the linking to user.lib? Angle, the missing VI's are probably OpenG VIs, these are must haves VI toolkits. Here's an installation video. Ton
  8. I haven't tried it but should it be like: MyObject Obj = new LVReferenceNumber(); Ton
  9. In the latest upgrades the button has vanished, could it be placed next to the 'manage topic poll' Ton
  10. Is there any reason to keep the reference active in between runs? You could use the 'Execution State changed' event for initializing and uninitializing the refs. Ton
  11. Name: Align Distribute Submitter: Ton Plomp Submitted: 28 Apr 2010 Category: *General* Version: 1.1.0 LabVIEW Version: 2009 License Type: BSD (Most common) Distribute objects v1.1.0 Copyright © 2009, 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 manager 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: 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 <organization>. 4. Neither the name of the <organization> 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 <COPYRIGHT HOLDER> ''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 <COPYRIGHT HOLDER> 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
  12. I'm using Mercurial and MantisBT for bugtracking, when I push something to my central repo a call-back script is run by Mercurial which informs Mantis of the commit, this works like a charm. However I would want to go further and implement the HGWeb Source integration. On top of that I have a Mindtouch wiki that lists all the open bugs and feature requests per project. Ton
  13. One of the nice things of a Distributed Version Control System (DVCS) like Git or HG/Mercurial is that you can easily commit your code on a daily basis. When working in a multi-developer team it can be quite scary to commit code, since it will end up with everyone. But by using a DVCS you can commit your code locally, and start developing a new feature and polishing the old code without sending it out while you can still go back to an intermediate version. Paul, please share your insights on the LabVIEW wiki page on Mercurial Ton
  14. Currently the search displays a message if the search term is too short. Ton
  15. The success of a community like ours is based on the quality of the questions. And last week I sprained my ankle and went on a business trip. Ton
  16. I don't like it. Now I have to go to the site to see what happened... I used to easily browse throught the posts, in a visual easy environment, no colors text only I would prefer two RSS feeds. Michael for your convenience I added a poll. Ton
  17. The RSS-stream (http://lavag.org/index.php?app=core&module=global&section=rss&type=forums&id=1) lost the info about the author of the post. I always find that very useful. Ton
  18. What's the type of your class? Is it a by-ref or by-value class? A by value class could explain this. Do you see the same amount of memory usage if you use a queue? For such intensive taskes (up to 2500 events per second) I would prefer a queue loop. Ton
  19. this is a great tool! I managed to launch 7.0, 7.1, 8.0, 8.6 and 2009 at once. ton
  20. Editing your code in the following way in the 'cluster' should fix your code: My code shows the edits in the array state, which should be in the cluster state. Remember that an array must have the same datatypes for all elements. Ton
  21. Getting way off topic, but COTS sounds like Vomit in Dutch... On topic, User Library Management is doable, however you need good discipline. And anything that helps you lowers the need for discipline. Ton
  22. In general LabVIEW paths will be stored relative, even if the target file resides on another drive (Windows only), you can see this in a lvprojectfile with a lot of ..\..\..\..\ On the other hand if the target file is inside instr.lib, user.lib or vi.lib an absolute path will be stored. One thing to try is to create an mnu file the old hard way (edit palettes) and look into the actual created mnu file with an hex editor. Ton
  23. I think it shows the frustration with jcarmody for not getting the feedback he wanted from you (amongst dealing with his own workload). Avinashgogineni, could you describe what currently is missing from the code we generously provided? Also we would find it very valuable if you show some effort in coding LabVIEW. Ton
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.