Jump to content

jcarmody

Members
  • Posts

    947
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by jcarmody

  1. I was thinking it meant something along these lines; I was a little slow on the uptake. I finally got it after it was spelled out. At least it resulted in another pun for this thread :)

    post-7534-125063337782_thumb.png

  2. What version of Camtasia are you using?

    I'm using 3.1.2 (they were giving free licenses several months ago).

    One more thing, in your Camtasia recorder options try enabling layered window recording.

    That did the trick. Thanks.

    The software demo's were done primarily with Camtasia Studio. The graphic animation section was done in Powerpoint and captured via Camtasia. I also had to do some Photoshop work on some of the images.

    It was this post that got me thinking along these lines, and also emboldened me to post this question in the Lounge. I love this community.

    Jim

  3. I would say that working full-time as a LabVIEW developer for a few years wouldn't hurt. ;) We had a thread in LAVA 1.0 from a gentleman that tried to go from LabVIEW zero to hero in short order. Does anybody remember how that worked out?

  4. From this point of view, the LabVIEW case structure is much less convenient to use than the other programming languages, image if we get more cases, we'll have to add more wires.

    :angry: Them's fightin' words! :angry:

    You can link tunnels so they're automatically wired when you add new cases. Right-click on an output tunnel and select Linked Input Tunnel and then Create or Create & Wire Unwired Cases.

    Notice the new glyph on the tunnel.

    post-7534-12503405833_thumb.png

    Picture made with the Code Capture Tool.

    v/r

    Jim

  5. I just noticed that if I drag/drop to reorder a section header the entire section follows it! I'm better than I thought - coding features before having the idea. :blink: I'll spend some time figuring out why this works tomorrow...

    Edit - the Tree Control does this, not my program. It turns out that I'm only as good as I thought (or, perhaps, not even).

    • When you duplicate a state, you could pre-populate the new name with the old state name (or ,may be even better, use the prefix such as if the state is "Macro: Initialize" the new state pre-populate name is "Macro:")

    The latest version does this. Thanks for the idea.

    new features I'd like to see:

    Rearrange Cases >> Alphabetically: I'd love to have a context menu item (in the tree) for "Rearrange Cases >> Alphabetically" (or similar). Note that this should ideally preserve the separators and groupings as are standard in the JKI State Machine.

    This is in the new version, too.

    Thanks,

    Jim

  6. Michael, thank you very much for your quick and kind reply, I have been doing just as you did, but I always got "Default" as the Label name, is there anything configuration that I didn't set properly?

    I can't see the Flash in Michael's post so I don't know if I'm restating something, but you seem to have a string wired to the Case Selector terminal. You make a case the default by right-clicking on the Selector Label and selecting "Make This The Default Case", not by typing it in.

  7. I like to hear that you're willing to share. I believe the BSD gives folks the most flexibility to use your work, but you'd need a lawyer to know for sure. I released something to the community under the BSD license without asking a lawyer because I don't care what folks do with it (I'm just tickled every time I see that it was downloaded).

    Now, your generosity aside, a commercial instrument company ought to be able to trade you something for your drivers...

  8. I was wondering if anyone has used Bugzilla http://www.bugzilla.org/

    In addition to managing bugs, could you use this tool to track requirements? You could tag each requirement as a "bug" and track when it was completed, and by whom.

    I had a discussion on NI's forum (during the LAVA outage) here, where managing requirements this way was mentioned; you're not the only one. I dunno about traceability.

  9. You can make it reentrant using the Execution.IsReentrant property. Then don't forget to set the Options terminal to 0x08 on the "Open VI reference" node.

    Two things:

    1. That worked. Thank you.
    2. VI Snippets are meaningless to me because we decided that there was no benefit in maintaining our SLA. I'll be working in 8.6.1 FOREVER...

  10. The NI Requirements Gateway interacts with the NI Unit Test Framework.

    I was thinking about that when I replied to Chris' post. One of the examples in the video gave an example of a requirement that a specified value had an indicator on the Front Panel. How can the Unit Test Framework validate that? A common requirement I'd have would specifiy a valid range for a measurement and the coverage would be code that tests for that. How would the UTF test that?

    I'm going to have to dig into a trial of RG.

  11. you've obviously put a lot of work into it

    Not so much, really. (It's built upon the JKI State Machine, which makes cranking out solid a proof-of-concept very easy. ;) ) It began as a fun attempt to use the LabVIEW API and grew.
    but since you asked... Did you develop it to a documented ISO audited and approved process?

    No.
    I need something that I know the vendor used an approved quality process, so I can be confident that the artifacts that it produces are complete and correct, and my customers can too. That's why I need to stick with Requirements Gateway for the time being - my customers can defend it because I can defend it because NI can defend it :)

    It would be great if, by demonstrating this tool, my managers would see the need for Requirements Gateway. I hope to learn more about this whole aspect of Software/Test Engineering because we don't do this here. I'm going to use this to give myself a warm/fuzzy feeling that I'm ready for SQA.
    Also, we do a lot of TestStand work and RG can dive into that too...

    That might be a problem, but maybe not. I think your first objective will be the show-stopper for most people.

    And another thing!!! My understanding (based on watching one of NI's videos) is that Requirements gateway looks for the same type of tag. But, finding one doesn't prove that the requirement is covered, it just brings you to the place where someone said it is. It still remains to be demonstrated that the purported requirement-covering code actually does what it's claiming to do, and that takes an auditor that understands the test language. No?

    Anyway, thanks for the feedback. I didn't sound too defensive, did I?

    Jim

×
×
  • Create New...

Important Information

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