Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/08/2009 in all areas

  1. Yippppeeeee My 100'th LAVA posting, I know that to many of you 100 posting is a mere blink of an eye. I have hardly made it into the foothill of great LAVA posting mountain, however I can now at least see the foothills. I do hope that some of my posts have been informative, been useful ... well lets be honest here ... been read. I was going to wait till I have something really usefull to say, before posting my 100th post, but hell I cannot wait that long cheers Dannyt
    3 points
  2. George I would strongly suggest that you investigate another option involving sub-panels and utilizing a listbox to choose the appropriate 'Page' (something like the LV Options page) Although tabs afford the user some good user interactivity points, it is limiting when attempting something more dynamic which it sounds like your doing. You will find that a listbox with subpanels are extremely more flexible albeit a hair more exotic with the process of getting information from the subpanels back to the top level.... but that is another discussion altogether with a variety of very good solutions. If you CAN NOT live without a tab control, you will still need to use sub-panels anyway and you would create the sub-panel VI on the fly with scripting and adding / removing tabs that way. (a creative yet very flawed solution) Good luck ~,~ Norm Kirchner
    2 points
  3. A PXI backplane is essentially a PCI bus with added signals for dedicated timing and synchronization. I'd use PXI if you're specifically looking for synchronization between cards. Other than that, and being different form factors, there's nothing else largely different between the two. PXI systems run either with an embedded controller (which typically run Windows, but could also run an Real-Time OS) or can be linked to a PC using an MXI cable. You'd program in LabVIEW the same you would on a desktop. Here's a page that describes PXI: http://zone.ni.com/d...a/tut/p/id/4811
    1 point
  4. Name: Ping dotNET Submitter: John Lokanis Submitted: 07 Jul 2009 File Updated: 03 Jan 2011 Category: Remote Control, Monitoring and the Internet LabVIEW Version: 8.6 License Type: Creative Commons Attribution 3.0 Ping dotNET v1.0.1 Copyright © 2009, John Lokanis All rights reserved. Author: John Lokanis LAVA Name: jlokanis Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 8.6.1 Dependencies: Requires .net 2.0 or higher Description: This VI performs a ping operation on the requested IP address or host name (requires DNS) the timeout for each ping as well as the delay between pings can be specified. The results are provided as arrays of each output type and in a text format designed to mimic the command line ping output. Instructions: Enter a valid IP address or host name and execute the VI. Known Issues: None. Acknowledgements: MSDN Change Log: v1.0.0: Initial release of the code. v1.0.1: Updates to the readme file and arrangement of the folder structure. (Mark Balla) License: Distributed under the Creative Commons Attribution 3.0 (http://creativecommo.../about/licenses) See link for a full description of the license. 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 "[CR]Ping dotNET" support page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org Click here to download this file
    1 point
  5. Here's an example of exactly that - a subpanel controlled by a list of categories (subVIs that are loaded into the subpanel). It's a half-arsed job that I was mucking around with, so use at your own risk. There are three VIs: the preferences dialog itself, a template preferences page and an example preferences pages (there are some OpenG dependancies that you'll need too). One added bonus is that the preferences dialog saves an ini file of all the values on the FPs of the preference pages, and recalls them from that file each time you show the preferences dialog again. The implementation I had it in would look in a particular folder for any VIs with "prefpage_" at the start of it's name, and attempt to include it in the category list. The top bar updates to the title of the subVI too. PreferencesDialog.zip
    1 point
  6. I think the 1 Million mark should obviously be... "Insane Object" The lowest rating in my mind would be "broken arrow"
    1 point
  7. Here's a quick and dirty way of doing what you want. It just shows or hides one window or the other based on a VIG. Run the Start Engines VI since it is the new top level one. It will run both the Login and Main windows. One will be shown the other hidden. Once the user presses the button on that window, it will hide itself and show the other, but they are both constantly running. EDIT: sorry I posted it in 8.6, now there is one for 8.5
    1 point
  8. Well, I finished my first scripting widget and I wanted to see what everyone thought. I got the idea from a *Wish List* post a while back. Why doesn't pasting simply replace the selected item? So here it is. Features: Copy something to the clipboard. Select another item(s). Press the Replace button or use the hot key to replace. It runs continuously on top and can have a hot key for Windows systems. It is written in 7.1 but it is 8.0 compatible (though the hot key recognition is not as nice, the LabVIEW system seems to get a hold of the keys a bit more than in 7.1). Structures are replaced entirely. If the classes don't match up, nothing is done. If nothing is selected, you have the option to do a normal paste, but this doesn't paste to where the last mouse click was (how do you get that?) There are different setup options that are changeable at run time. Download File:post-1519-1144715140.llb Tell me what you think. David
    1 point
×
×
  • Create New...

Important Information

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