Jump to content

Darren

NI
  • Content Count

    579
  • Joined

  • Last visited

  • Days Won

    48

Everything posted by Darren

  1. Rolf is right...there's no need to run a LabVIEW patch (like an 'f1') unless you are experiencing the exact issue described as fixed in the patch. The Service Packs, on the other hand, will contain several bug fixes and potential performance enhancements, and are intended for all users of that particular version.
  2. I posted a utility VI that does this here. -D
  3. As promised, here's my blog post on creating your own Quick Drop keyboard shortcuts in LabVIEW 2009. -D
  4. Yes, the keyboard shortcuts in Quick Drop are a plug-in architecture. Look for a post on my blog soon that describes how to write your own keyboard shortcuts for Quick Drop. As for Shaun's issue, I'm totally stumped as to why your shortcuts aren't working, short of some strange configuration of your keyboard that is messing with the Ctrl modifier key. With a clean install of LabVIEW 2009 on a Vista machine, I can select an object, then press Ctrl-Space, Ctrl-D, and the controls/indicators are created. -D
  5. Are you sure you're running LabVIEW 2009 and not 8.6? Assuming you are in LV 2009, check in [LV]\resource\dialog\quickdrop\plugins. Do you see three VIs there, called d.vi, r.vi, and t.vi? If you do, open them. Do they have a broken run arrow? Keep me posted, -D
  6. I will certainly admit that the placement within Quick Drop of the new keyboard shortcuts isn't the most ideal location for the feature (although it is documented in the Keyboard Shortcuts topic in the LabVIEW 2009 Help). But before deciding to spew forth vitriol against a feature you can freely choose not to utilize, please note that the following conversation has already taken place several times within the walls of NI over the past few months: QD Fan: "Hey Darren, I really like the new keyboard shortcuts in Quick Drop!" Darren: "Thanks!" QD Fan: "One question though, why do I have to l
  7. I got your twitter DM this weekend, but haven't had a chance to respond until now. I got the reference immediately (rusty nail through the heart, still love scripting, etc. etc.), and yes, I thought it was cool. -D
  8. http://www.twitter.com/dnatt I should be down there tweeting all day Tuesday, Wednesday and Thursday (see my tentative schedule here). -D
  9. Ok, I had a few minutes this afternoon to re-read this thread and look into any low-hanging fruit for improving the performance of the MD5 VI that ships with LabVIEW. Unless I missed something, there were three concrete suggestions for improving the performance of the core VI: 1. Disable debugging: Done. 2. Move Swap Words and Swap Bytes functions out of the loop: Done, although this appears to have a negligible effect compared to turning off debugging. 3. Process file as a U32: I haven't done this one yet. JFM, can you post your modified version of the VI so I can take a look at it
  10. QUOTE (Phillip Brooks @ Jun 11 2009, 08:30 AM) Thanks, Phillip. I have filed CAR# 173651 to myself for investigating your suggestions in LabVIEW 2010. If anybody else has any suggestions, post them here, as I will be reviewing this thread when looking into the CAR later this year. Again, I'm looking to stick with a 100% G, platform-independent implementation. -D
  11. I own the one that ships with LabVIEW. If y'all figure out a way to implement it with 100% G code (i.e. no command line calls) that's faster than the current shipping code, I'd certainly be open to changing it in LV 2010. This topic came up a few years back on LAVA, and at the time, mine was quite a bit faster than the OpenG one. -D
  12. QUOTE (Norm Kirchner @ Jun 8 2009, 04:10 PM) More details about the traverse VI http://labviewartisan.blogspot.com/2009/06/labview-scripting-tip-1-power-of.html' rel='nofollow' target="_blank">here. -D
  13. QUOTE (lavezza @ Jun 5 2009, 03:56 PM) The MenuLaunch.App and MenuLaunch.VI properties are private, which means they are not exposed in scripting. It would not be unreasonable, however, to expect a VI that wraps these properties in a future LabVIEW version. -D
  14. My 2nd blog post on scripting: LabVIEW Scripting Tip #2: Supporting Undo -D
  15. Try using a Case Structure...if the reset button is pressed, wire an empty string to the display (and into your feedback node). Otherwise wire in the string you're keeping in the feedback node. -D
  16. QUOTE (asbo @ Jun 3 2009, 07:43 PM) Heh, maybe. We'll see what my time availability looks like in the coming weeks. Don't forget I have to come up with Weekly Normal Nuggets, too. And I should probably figure out here pretty soon what I'm going to present at NI Week. -D
  17. My first blog post on scripting: LabVIEW Scripting Tip #1: The Power of Traverse -D
  18. QUOTE (jdunham @ May 21 2009, 12:00 AM) I have a Quick Drop shortcut of 'nc' for Numeric Constant...I use it all the time to drop an I32 constant. I could see it being useful for a DBL constant to be on the palettes, simply so I could have a 'dc' shortcut to drop the DBL constants when I need them. I'll look into what it might take to get a DBL constant added to the palettes sometime in the future (the work would be trivial, it's just a matter of convincing the right people). For now, though, you could add your own DBL constant merge VI to the user.lib palettes, and use Quick Drop to ha
  19. QUOTE (Black Pearl @ May 13 2009, 02:21 PM) Hah, I just realized that at some point in the past, I changed my profile to include LV 2009 too. To add credibility to my previous statement, I've changed it back to only list the released LabVIEW versions I use. -D
  20. QUOTE (crelf @ May 13 2009, 11:42 AM) I agree. I don't think it makes sense to list an unreleased LabVIEW version as an option when setting up a LAVA profile. -D
  21. QUOTE (Aristos Queue @ May 8 2009, 02:01 PM) I don't consider it a blind spot. My http://forums.ni.com/ni/board/message?board.id=170&thread.id=380412' target="_blank">favorite feature of LabVIEW 8.5 was the For Loop with Break. I've probably used it hundreds, if not thousands, of times in code I've written in the past 2 years. And the few times I've needed the index of the For Loop when it stopped, I just used the iteration count within the loop. If I ever needed to know how many times the loop ran, I would just drop an increment in the loop and wire it to the iteration count.
  22. Also, the CLD is a 4-hour application coding exam, there aren't any "questions" on it to speak of. And this is too specific a question for the CLA. And probably too difficult for the CLAD. -D
  23. QUOTE (gmart @ Apr 21 2009, 11:01 AM) I'm pretty sure the most advanced feature on that calculator is that you can type in "5318008" and turn it upside down. -D
  24. QUOTE (TobyD @ Apr 21 2009, 10:05 AM) That's hilarious. Man, this is so cool that there's HP calculator zealots here. I guess it goes with the territory, though...you guys all have impeccable taste in programming language, so it only makes sense that you'd all like the best calculators too. -D
  25. QUOTE (Mark Yedinak @ Apr 20 2009, 05:26 PM) Awesome! I had an engraved name plate on my 48GX! I still contend the 48G series was the best graphing scientific calculator ever made (always bugged me that TI-85 was the standard in my high school). A few months back I reluctantly sold my 48GX, since I haven't used it since undergrad college. I sold it in 2008 for as much as I bought it for back in 1993! -D Oh, and in case anybody wants to start a calculator debate (snicker), I contend that the HP 32SII (which I still own) is the best non-graphing scientific calculator ever made. 384 by
×
×
  • Create New...

Important Information

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