Jump to content

Darren

NI
  • Content Count

    560
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by Darren

  1. Darren

    Annual LAVA/OpenG BBQ

    QUOTE(crelf @ May 23 2007, 02:43 PM) My rudimentary web searching skills are revealing the largest ranch in Australia to be about 30,000 sq. km, and Texas is about 680,000 sq. km. What else you got, Dundee? -D
  2. Darren

    Annual LAVA/OpenG BBQ

    QUOTE(xtaldaz @ May 23 2007, 02:12 PM) I wear my 'Large' LAVA shirt sometimes anyway, even though it makes me look like I should be in a Will Ferrell SNL skit. Some chick in downtown Austin actually asked me one time (when I was wearing my shirt) what LAVA was. Her eyes glazed over after I mentioned computers. I think next time I'll make up something about volcano worship. -D
  3. Darren

    Annual LAVA/OpenG BBQ

    QUOTE(xtaldaz @ May 23 2007, 02:00 PM) I wish I'd known you had an XL LAVA shirt when you still worked here, Crystal...we could have traded! -D
  4. QUOTE(Tomi Maila @ May 23 2007, 01:31 PM) The feature I've been wanting that would be well-suited for one of these mythical "XNodes" would be a growable Array Size function, that returns 'n' scalar "dimension size" outputs, where 'n' is the number of dimensions of the array. I would much prefer this to the current method of dropping an Array Size and an Index Array. -D
  5. Darren

    Annual LAVA/OpenG BBQ

    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.
  6. Darren

    sEQEUNCE

    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
  7. Darren

    sEQEUNCE

    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
  8. Darren

    Annual LAVA/OpenG BBQ

    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
  9. Darren

    Annual LAVA/OpenG BBQ

    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
  10. Darren

    Annual LAVA/OpenG BBQ

    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
  11. 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 instances of Globals, you can ignore the "Types of Globals to Detect" option on the config page (I added this for somebody who needed to only find a certain type of a certain global). This VI Analyzer test is saved in LabVIEW 8.2.1 and is only compatible with VI Analyzer 1.1 and later (the current version as of today is 1.1). I hope it helps, let me know if you have any problems using it. -D
  12. 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.
  13. 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
  14. 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
  15. 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 to NI Tech Support, who sends all of these error reports on to LabVIEW R&D. If you can reproduce the DWarn/DAbort with some simple steps, it would also be helpful to submit a sample VI (if applicable) along with the error log. Hope this clears up the issue, let me know if you still have any questions. -D
  16. 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
  17. 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.
  18. QUOTE(crelf @ Apr 5 2007, 03:12 PM) I'm guessing jaec gets his crack from here. -D
  19. 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 have a game called Numbers Challenge where you are given a card with 4 numbers between 1 and 9, and you have to try to reach the target number (anything between 0 and 20 is possible) using only simple operations and all 4 of the numbers on the card. I wrote a VI that proves that all targets between 0 and 20 are possible with every card. A math whiz gave me the game a long time ago, and I didn't believe him when he said any number between 0 and 20 was possible with every card...but LabVIEW proved he was right!
  20. 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 manipulating UI elements, I simply unbundle whatever references I need from that cluster. If I have a subVI that needs the references, I pass the cluster into the subVI via its conpane, and then unbundle whatever references I need within the diagram of the subVI, as seen here: http://forums.lavag.org/index.php?act=attach&type=post&id=5393 I hope these screenshots help illustrate my method. It's very easy to deal with front panel controls with VI Server when you have access to any of the control references you need at any point on the diagram. If there's another control I need access to, I simply add it to the Bundle By Name (and the typedef). To make things easier for me, I also keep the control references organized alphabetically in the typedef cluster by changing the Cluster Order whenever I add elements to the cluster. This gives me an alphabetized list whenever I operate-click on an Unbundle By Name to select the proper reference to unbundle. Let me know if you need any more clarification on this method. -D
  21. 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 and makes the code very fast. This is the approach I take in all my UI VIs (i.e., any app where I will be programmatically modifying UI elements). -D
  22. ...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
  23. 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...
  24. 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...
  25. Sounds like a good feature request...the List Folder function currently does not support specifying multiple patterns on the 'pattern' input. -D
×
×
  • Create New...

Important Information

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