Jump to content

Darren

NI
  • Content Count

    580
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Darren

  1. It's all about what you're used to. I've spent my entire life in central and south Texas. I have no clue how to drive a vehicle when the roads are icy, and I don't even try. And I'm not afraid to admit it. ...but then again, I can also spend the entire day outside in July when it's 105 and not drop dead. We all have our strengths and weaknesses. -D
  2. I added VI wrappers with error terminals for Wait (ms), Wait Until Next ms Multiple, and Tick Count in LV 2011. Look for them in vi.lib\Utility\timing. They're not the ideal solution, but until we get error terminals on the primitives, at least we can stop having to worry about maintaining our own copies. -D
  3. Me. Whenever I want a new LabVIEW feature, I just walk over to some C-Monkey's desk and ask him for it.
  4. I just tried a simple use case on my machine and it worked fine. I saved a VI in LabVIEW 8.6. I ran the VI Analyzer on that VI in 2010. I saved the .rsl file next to the VI. I opened 8.6 and loaded the .rsl file, and was able to highlight failure results without errors. Do you have the VI Analyzer Toolkit installed in both LabVIEWs? Are you highlighting test results for tests that are present in both versions (some tests were added in 2009 and 2010)? Are you keeping the .rsl file in the same place? The .rsl file stores VI paths relative to itself, so the .rsl file shouldn't move after
  5. That looks shopped. I can tell from the pixels. Plus, I've seen lots of shops in my day.
  6. It's also the Windows username of one of our marketing managers. So I'm going with 'coincidence' on this one. But of course, that's probably what y'all expect me to say.
  7. The Get VI Dependencies method (which replaced Callees as the preferred way to get a VI's hierarchy info) seems to work inside an EXE for me: -D
  8. Here's a VI that will give you the path to your LabVIEW INI file. Works on all desktop platforms in LabVIEW 8.0 and later. -D LabVIEW Preferences File Path.vi
  9. I just did a search...those methods are not used anywhere (including the Property Pages) in LabVIEW 2010. I have an educated guess as to their purpose, though. Back when the Property Pages were first added to LabVIEW in version 7.0, there were many properties of VI objects that were not yet exposed in VI Server. As a result, the Get/Set Object methods were added, and hard-coded indices to an internal database of properties were used for getting/setting properties of controls. As the VI Server interface to objects improved, this mechanism was no longer needed, as evidenced by the fact that
  10. Versions 1.0 and 1.0.1 of the Report Generation Toolkit did not include any logic for attempting to keep other windows open. This logic was added in version 1.1: Version 1.0.1 of Excel_Quit.vi Version 1.1 of Excel_Quit.vi According to this webpage, you can use up to version 1.1.2 with LabVIEW 7.1. I'm not sure if it's a free upgrade or not, so you should probably check with your NI salesperson. Good luck, -D
  11. I've gone down that path before...it's fraught with peril. Example: Grab the scrollbar (mouse down), move your mouse out of the tree bounds (mouse leave), and with your finger still down, drag the scrollbar up and down. All of a sudden, you're not getting events anymore, even though the displayed items are changing. That's why polling is the simplest solution for now...unless you want to implement your own scrollbars. -D
  12. I can't think of an event-based solution, but there is a pretty straightforward way if you don't mind polling the tree: (If you drag this snippet to your diagram, you'll need to replace the reference control with a Tree reference so it will run) This code will give you the tags of all visible items in the tree. If you poll this, and store the tag array in a shift register, you can compare against the previous iteration to see if it changed, and update the visible tags accordingly. -D
  13. These are the ones I use...I use shortcuts for functions and VIs as much as I use them for structures: Quick Drop Palette Object Shortcuts for Right-Handed Developers -D
  14. When processing an array of SubVI references, I always pass each of them through this VI (included in LabVIEW 8.6 and later...prior versions require the VI Analyzer Toolkit to be installed): vi.lib\addons\analyzer\_analyzerutils.llb\VIAnUtil Valid SubVI.vi This VI will return FALSE if the SubVI reference is an Express VI or a "?" missing subVI. It returns TRUE otherwise. -D
  15. I had a similar problem with PayPal many years ago. I haven't used them since (notice how Christina bought my LAVA BBQ ticket this year?). My respect for LAVA would only increase if y'all dumped PayPal. http://paypalsucks.com/ -D
  16. Darren

    jgcode

    Sweet, my feature has a nuthugger. And yes, I had to go look up what a nuthugger is. -D
  17. His looked like this...a 15-segment display, if you will... -D
  18. Nobody has ever beaten me, and nobody ever will. Now *that's* a call out... -D P.S. - I need to have a talk with the judges next year about literal interpretation of the rules, because Robert's answer for the 7-segment display was NOT a 7-segment display. Thankfully he messed it up just a little bit, which gave me enough time to finish my real 7-segment display while he tried to fix his...
  19. I believe it's asking how much time you're willing to give LabVIEW to perform the action. For example, a frequent editor action, like wiring two terminals, you would expect to be a "trivial" amount of work, i.e. LabVIEW should be able to perform the action immediately. But for something else, like building an EXE, you would probably expect LabVIEW to spend more time, and be ok with that. I don't particularly like how that option is worded, but that's my understanding of what it's supposed to mean. -D
  20. As I mention in my blog post, Requirements Gateway is only used for *grading* the exam. You don't need to know Requirements Gateway in order to *take* the exam, you just need to follow the instructions in the exam regarding how to document requirements tracking in the code you write. -D
  21. Thanks for posting this, JG. I have written a new post on my blog regarding the changes to the CLA exam.
  22. That was pretty funny. Good thing they didn't reserve that one for me... -D
  23. <-- member of LabVIEW R&D
  24. I'm in, and my Durango seats 7. Who's riding shotgun?
  25. Yes. It may be 110 F outside, but they keep it at around 45 F inside. Bring your mittens! -D
×
×
  • Create New...

Important Information

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