Jump to content

Darren

NI
  • Content Count

    582
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Darren

  1. The keyboard shortcut for the Revision History dialog box in LabVIEW is Ctrl-Y. Could there be some config option in the Windows speech settings that is making it try to convert whatever you're saying into a Ctrl-command? Just a thought, -D
  2. I think I've seen this issue posted on the NI Forums a few times, and I think it has to do with having an Event Structure in your 2009 diagram and attempting to save to 8.5. I think there are some workarounds posted. -D
  3. Be careful with that, as there are some problems when converting null data from a database with the regular Variant To Data function that the DB Variant To Data function handles correctly. Also, I think the Timestamp issue was fixed in the Database Toolkit at some point, but I don't remember which LabVIEW version it was. -D
  4. I posted a response in the thread on the NI Forums...I think we should probably continue the conversation there since it has the entirety of the conversation. -D
  5. Yeah, I used to play the games on here a lot, but there's so many alternatives at this point that it probably doesn't make sense to put any effort into bringing them back here...well, unless it's a gallery of LabVIEW-based games, that is... -D
  6. The new LAVA doesn't have any games. I haven't heard Michael mention bringing them back, either. -D
  7. The VI Analyzer Spell Check test harvests all the words from a VI...you could probably steal some of its code to find words and replace them. -D
  8. From one CLAburger to another, congrats! -D
  9. Even though you can't get official support from NI for the older versions, I'm running LabVIEW 7.0, 7.1, 8.0, 8.2, 8.5, 8.6 and 2009 on my Windows 7 64-bit machine and haven't seen any problems with any of them, installation or otherwise. -D
  10. I filed CAR# 191973 on this issue. Unfortunately, I don't know of a workaround. -D
  11. 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.
  12. I posted a utility VI that does this here. -D
  13. As promised, here's my blog post on creating your own Quick Drop keyboard shortcuts in LabVIEW 2009. -D
  14. 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
  15. 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
  16. 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
  17. 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
  18. http://www.twitter.com/dnatt I should be down there tweeting all day Tuesday, Wednesday and Thursday (see my tentative schedule here). -D
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. My 2nd blog post on scripting: LabVIEW Scripting Tip #2: Supporting Undo -D
  25. 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
×
×
  • Create New...

Important Information

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