Jump to content

Darren

NI
  • Content Count

    581
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Darren

  1. Hey, if there's another T-shirt giveaway at the BBQ, make sure to bring plenty of Extra-Larges this time. Remember, everything's bigger in Texas. -D P.S. - Seriously, I'm guessing you guys like the idea of me wearing a t-shirt with a big ol' LAVA logo to work...but I'm guessing my LabVIEW R&D colleagues don't want to see me in a tight t-shirt of any variety. P.P.S. - haha, I'm glad to see my 100th LAVA post was something classy like this.
  2. QUOTE(Jim Kring @ May 18 2007, 09:46 AM) Hey Jim, Seeing your post reminded me of a similar technique I use for debugging Event Structures. You inspired a http://forums.ni.com/ni/board/message?board.id=170&message.id=248138' target="_blank">Darren's Occasional Nugget today! -D
  3. QUOTE(BrokenArrow @ May 18 2007, 10:14 AM) I know a lot of people have wrapped the Delay function in a subVI and given it error I/O...if you do this, you can put your Delay "subVI" at the end of your error chain in your loop, guaranteeing it runs after all the other code in the loop. -D
  4. QUOTE(yen @ May 18 2007, 06:06 AM) I saw the "Null Vote" text, but kinda didn't think about it. This is the only on-line survey I've ever encountered where viewing the results counts as a vote. I'll make sure to register what the words "Null Vote" actually mean the next time I read them... -D
  5. QUOTE(Herbert @ May 17 2007, 06:12 PM) County Line on the Lake does provide an all-you-can-eat group deal...at least they did when I went there in Fall of 1998 with about 100 other senior engineering students... -D
  6. QUOTE(Aristos Queue @ May 17 2007, 03:15 PM) Hey, at least you got to vote...it says I've already voted, but all I did was view the results without voting. I demand a recount! Actually, I was also going to pick "somewhere else" since the Salt Lick is in BFE, but I really couldn't think of a venue in Austin that can accomodate such a large party and provide the amount of food that The Salt Lick provides. Bring on the meat! -D
  7. Alrighty, here it is. Create a directory under your My Documents\LabVIEW Data folder called "VI Analyzer Tests". Put the attached LLB in that folder. Now, the next time you launch the VI Analyzer, you'll have a new category in your tests list called "User-Defined Tests" that contains the Find VI Calls test. With this test, you can specify the names of VIs (as strings), and the test will find any instances in your VIs of subVI calls to this VI name, along with any string or path controls/constants that contain the VI name (in case you're calling it dynamically). If you're not looking for i
  8. Do you have the VI Analyzer? If so, I've written a test in the past that will do this subVI search. It doesn't ship with the VI Analyzer though...let me know and I can dig it up and post it. -D P.S. - If you're not sure whether or not you have the VI Analyzer, it's included in the Dev Suite, or sold separately as an add-on toolkit.
  9. QUOTE(i2dx @ May 2 2007, 12:42 PM) That reminds me of a line from the now-canceled HBO show "Lucky Louie": "Do you know how much money we have in our bank account? Negative 50 dollars. We have to *raise* 50 dollars to be broke." -D
  10. My LAVA Inbox currently has -1 messages (check out the upper right corner of the image): http://forums.lavag.org/index.php?act=attach&type=post&id=5693 -D
  11. There are a couple of internal errors in LabVIEW called "DWarns" and "DAborts". You'll get that dialog on launch if a DWarn or a DAbort occurred on the previous run of LabVIEW. A DAbort is a crash, but a DWarn could be some internal error that LabVIEW logged, but LabVIEW was still able to continue operating normally. If you click the "Investigate Internal Error Now" option, you'll be taken to a webpage that will perform a search of the NI Support site to see if that internal error has any KnowledgeBase entries associated with it. Assuming your error does not, you can submit your log file t
  12. The 8.2.1 installer is a full installer, so all of the VIs it installs are already mass compiled in 8.2.1. The install takes longer than an 8.20 install since the 8.2.1 installer actually uninstalls each 8.20 component before it installs the 8.2.1 components. -D
  13. QUOTE(gleichman @ Apr 9 2007, 02:51 PM) There are other Report Generation Toolkit LLBs that get overwritten by the 8.2.1 install besides NIReport.llb. I recommend uninstalling the toolkit first, then installing 8.2.1, then reinstalling the toolkit (this problem is mentioned in the 8.2.1 readme). -D P.S. - We are looking at ways to ease the LabVIEW/RGT integration pains in a future LabVIEW version.
  14. QUOTE(crelf @ Apr 5 2007, 03:12 PM) I'm guessing jaec gets his crack from here. -D
  15. I've never seen that show before...that is definitely my kind of show! Just to get a clarification on the rules...you have to use all 6 numbers in your solution exactly once? And only simple operations (add, sub, mult, div) are allowed? The target number is anything between 0 and 999? What's the name of this show? Looks like it's an old show, and I'm guessing they have other categories on the show besides math (judging from the encyclopedia or dictionary on the host's desk). Good stuff, -D P.S. - I've already written LabVIEW code that solves a puzzle like this, although simpler. I hav
  16. Here are a couple of screenshots to illustrate the method I described. These are actually snippets of code from the VI Analyzer UI. Here is the code during initialization of the main UI that bundles control references into the typedef cluster...these are references of any controls and indicators that I need to programmatically manipulate throughout the execution of my UI code: http://forums.lavag.org/index.php?act=attach&type=post&id=5392 This cluster is wired to the border of my main event structure for my UI. In any case of the event structure where I am programmatically manipul
  17. The way I get around this issue is to create a typedef cluster containing control references to any control I wish to programmatically manipulate within my application. I bundle by name all my control references during code initialization, then unbundle the references whenever I need them in other places in my VI. If I need any of these references in a subVI, the typedef cluster is on the conpane of the subVI so I can unbundle the reference(s) I need within the subVI. Since it's a typedef, I can add control references to it as I develop code. This avoids any array searching for references
  18. ...and while we're talking about breakpoints, don't forget the nifty "Remove Breakpoints from Hierarchy" feature in LabVIEW 8.2 that will remove all the breakpoints from the hierarchy of a VI, so you don't have to go searching for any breakpoints you may have left in the diagram of your VI (or any of its subVIs) while debugging. -D
  19. Hey now, the fact that I work at NI has absolutely nothing to do with the fact that I'm totally pwning all of you in the LAVA arcade... -D P.S. - And to further fuel the flames, I will go on record as saying that there is NO WAY you people can EVER dethrone me as the LAVA arcade champion. NO WAY! Well, I guess you'd have a chance if Michael reset all my scores...
  20. I've only made it to level 14, and I noticed that the left-most pipe seems to be the "fake" one. I only determined this by losing, then clicking "retry" after losing, since the "retry" lets you start over on the same level you just lost (unfortunately, your score is reset). -D P.S. - As for having "waaaaay too much time for playing games in the arcade", I'm currently in the middle of 5 weeks of paternity leave, and my older kids (not the newborn) *love* to watch me play [wiki]LAVA[/wiki] arcade games. Plus, it's a good time-killer when trying to rock a baby to sleep...
  21. Sounds like a good feature request...the List Folder function currently does not support specifying multiple patterns on the 'pattern' input. -D
  22. Wow, I didn't know the menu ring worked with Call By Reference nodes. But I just tested and apparently it does. -D P.S. - In my original post, I mentioned that the order is "top-down"...actually, the top of the hierarchy of calls appears at the bottom of the list, and the direct caller of the VI with the breakpoint is at the top.
  23. Assuming you're not dealing with dynamic VI calls, you can view the call stack ring in the toolbar when a breakpoint is hit in a VI. It's normally the font ring, but when you have a running VI that is paused at a breakpoint, it becomes a call stack ring, with a top-down list of the VI call hierarchy all the way down to the VI with the breakpoint. -D
  24. This same question was posted on the NI Forums last week. I don't know if it was by the same guy or not. Here's my reply. -D
  25. Unflatten has been pretty stable for me in LabVIEW 8.2. But fine, here's another way, although this one is 48x48 pixels instead of 32x32: This was my first idea, and would probably be the easiest to wrap with one of these mythical "XNodes" I keep hearing about. -D
×
×
  • Create New...

Important Information

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