Jump to content

Leaderboard

Popular Content

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

  1. Name: CaseSelect Submitter: jcarmody Submitted: 08 Aug 2009 File Updated: 03 Jan 2011 Category: JKI Right-Click Framework Plugins LabVIEW Version: 8.2 License Type: BSD (Most common) Copyright @ 2010, Jim Carmody All rights reserved. Author: Jim Carmody jim@jamescarmody.com CaseSelect is a plugin for the JKI Right-Click Framework for LabVIEW and is distributed as a VIPM package. Introduction I make State Machines with many, many states; perhaps you do, too. I don't like scrolling through long lists of states and have wanted to have a scroll bar on the drop-down list. This plug-in launches a new panel with a Tree control (one that has a scroll bar) containing each of the Case names. Features Select a case in the CaseSelect window and it comes to the front in your Block Diagram JKI State Machine states are indented in the Tree control CaseSelect window floats and can be resized Open multiple CaseSelect windows at the same time to work with more than one Case Structure Select a case with the mouse or navigate the Tree using arrow keys Insert & delete states with Insert/Delete keys or context menu (Insert suggests new name based on section header) Reorder cases with drag/drop Ctrl+drag/drop to duplicate a case (suggests new name based on section header) Collapse/expand all tree elements with context menu Sort cases alphabetically (preserving the section headers of a JKI State Machine) New in 2.0.1 I'm pretty bad at keeping track, but here are a few... Renaming a case triggers a search-and-replace for all instances of the old name in all String Constants Select a String Constant in your VI and double-click a case in CaseSelect and that will be appended to the String Constant - build macros quickly New in 3.0.0.4 (currently only for LabVIEW 2010) I'm still pretty bad at keeping track, but I made a new package. Added navigation buttons to move back and forth through the states you've visited (history) ~ still buggy The original discussion of this can be found here. Click here to download this file
    1 point
  2. Whooo Hooo, it came through!! I'm really happy to be at this point, its a new direction for me but one that will be a lot of fun, and bloody hard work. Thanks to the guy's at NI Australia for your support
    1 point
  3. Thanks to Todd for this one: http://bit.ly/6ijVk
    1 point
  4. Feri, I tried to attach some screen shots for you, but the site seems to hang when I do this. I have done what your wanting to do with a couple of old HP VNAs. The problems with mine are that there was no real good way to display the data direct. I ended up doing some graphic overlays with a transparent background and placed them over an X-Y graph. This way I could display polar, Smith, etc. on the same graph. This worked very well for a generic type program. The one VNA I have has a built-in SOLT calibration, the other does not. So I just wrote this in Labview. In some cases I just wrote programs for a specific test. Easier than trying to make a generic program that would do everything. Do you have the programming manuals? If so, this shouldn't be too hard to get working. More time consuming than anything. If you run into a specific question and have the manuals, maybe I can help.
    1 point
  5. By popular demand1, I have reattached the Exterface Architecture example following the LAVA meltdown of 2009. The project is saved in 8.6. Be sure to review the readme files in the various project folders; they will help explain what parts of the project I consider part of the application, which parts are Exterface framework, and which parts are there simply to enable the demo to run. There is a first draft document in Word format that gives a broader explanation of what I was trying to accomplish. I also created this UML class diagram that hopefully helps explain what I did. In the months since I created this I've discovered this idea is essentially an implementation of the adapter pattern. The top diagram2 illustrates the adapter pattern. The bottom diagram shows the Exterface Architecture in the context of the adapter pattern. The blue blocks are the components I added to compensate for the lack of object references in LV8.6. I have a couple other implementations I've been working on that also enable Interface-like behavior. I don't yet have a good feel for they stack up against each other but my sense is this will be the most restrictive. With the release of object references in 2009 I suspect this model can be simplified using DVRs. Dave 1 Popular demand = 1 person 2 Model shameless copied from Head First Design Patterns and recreated in StarUML. Exterface Architecture.zip
    1 point
  6. At the (fantastically awesome) LAVA/OpenG BBQ, someone (apologies to whoever it was, I forget who - sometimes I think I'm the Dory character from Finding Nemo) asked about getting more recent projects in the GSW. Stephen Mercer / Aristos Queue had provided modified versions of the VIs to do this in 8.6. I added a config token for this in LV2009, so you no longer need the modified VIs. It's MaxGSWRecentProjects=10 (or whatever other number you want. We never display more than 10 recent files, though). - Christina, aka "Miss Eyes on VIs," LabVIEW R&D
    1 point
  7. Hey guys, I have cracked it - fixed the solution and potentially found something that may have been causing the issue... 1. After installing LV 2009, I ran VIPM to put the OpenG stuff into the new version. Doing this, It seemed that not all of the packages were installing properly, so I gave up with the intention of looking further when things are a little quieter in the office. 2. Looking in the QuickDrop folder, I noticed some of the VIs had different dates (which was I thought was a little odd), and more importantly there was a VI called QuickDrop Launch Window - BACKUP.vi 3. I opened the QuickDrop main launch window directly (dropping it as a subvi to avoid the run when launched effect) and tried to view the BD (and couldnt due to password protection). When I couldn't I deleted it and was prompted to save a couple of files... one of which was called Enable VOice COmmand and appeared to be something associated with LV Speak. 4. I put two and two together, removed the QD Launch Window and the Enable VOice Command VIs, and renamed the BACKUP file. 5. QD now works with shortcuts! :-)
    1 point
×
×
  • Create New...

Important Information

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