Jump to content

Darren

NI
  • Content Count

    581
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Darren

  1. QUOTE (neB @ Aug 11 2008, 12:44 PM) On my 3 GHz, 2 GB RAM machine, here are my times. This is LabVIEW 8.6, pretty much every module and add-on installed (and the default drivers too) from the LabVIEW 8.6 Platform DVD: Load Palettes in Background: LabVIEW launch time - 8 sec Initial Quick Drop launch time - 4 sec Load Palettes on Launch: LabVIEW launch time - 12 sec Initial Quick Drop launch time - 0 sec So I'm seeing that the total time is effectively the same. Note that this is a non-initial launch of LabVIEW after a reboot. I expect the times would be a fair bit higher if this
  2. QUOTE (ragglefrock @ Aug 11 2008, 12:24 PM) Change the setting to "Load Palettes on Launch" if you want all Quick Drop info to be ready to use when LabVIEW launches. Depending on how many toolkits, modules, add-ons, etc. you have installed, your launch time will increase a certain amount. I've never seen a 45-second wait, though. Is your computer reasonably fast? -D
  3. Yes, I encourage all of you to send feedback on this issue (and any others you had at NI Week 2008). My presentation started at 10:30 on Thursday, and the tiny room was completely full by 10:10, with a bunch of people outside trying to get in. They had to kick out some NI employees who were sitting on the floor to make room for paying customers to sit on the floor. I don't know if this is its intended purpose, but it seems to me the NI Week Discussion Forum over at ni.com might be a good central location to submit this feedback. -D
  4. QUOTE (jlokanis @ Aug 9 2008, 12:54 AM) I don't count the Basic programs I wrote on my Atari 400 as a kid, or the Pascal I was required to do in high school. Yes, the Quick Drop window in LabVIEW 8.6 is pure G. The only C work that needed to be done was the addition of a couple of private VI Server properties to give me palette object name information. Those properties were written by the person who was familiar with the palette source code. Oh yeah, and the guy who owns the menu source code added a snippet to launch my Quick Drop VI from the menu (or most commonly, from its menu short
  5. QUOTE (jgcode @ Aug 8 2008, 05:22 PM) I demoed Quick Drop during the Tuesday keynote at NI Week, I used it extensively during the LabVIEW Coding Challenge yesterday at NI Week, and there is a video of me using Quick Drop on the Quick Drop webpage. There's currently an awesome viral video making the rounds of some guy at NI Week who uses Quick Drop to generate beers on his desk, but that one is *not* me. -D
  6. QUOTE (Val Brown @ Aug 8 2008, 02:41 PM) I have never programmed in a text-based language, and I'm the one who wrote Quick Drop! At the end of the day, I have a beautiful, graphical program in front of me, and I was able to create it faster with Quick Drop than I could have with the palettes. That's why I wrote the feature. For me, using the keyboard to instantly drop an object (the name of which I already know) is much faster than trying to find it in the palettes, over and over again. ...and all of my user-defined shortcuts are left-handed, so my right hand rarely needs to leave th
  7. QUOTE (neB @ Aug 8 2008, 09:34 AM) As Stephen indicated, you don't need to configure shortcuts (although they are invaluable to me personally). Every single item in your current palette set will be available to drop with Quick Drop. The object names are auto-completed for you as well. On my LabVIEW 8.6 install, merely typing 'fo' and 'wh' are enough to auto complete For Loop and While Loop, respectively. I prefer using shortcuts, though ('fs' and 'ws' for For Loop structure and While Loop structure), since I don't have to worry about some other object appearing in the palettes and scre
  8. QUOTE (neB @ Aug 7 2008, 03:15 PM) If you are in fact using LabVIEW 8.6, why are you going to the palettes to drop a For Loop? P.S. - One of your colleagues at NI Week said 'hi' to me today on your behalf, but I forgot already who it was...you'd think the guy who wrote Quick Drop would be better at remembering peoples' *names*... QUOTE (Aristos Queue @ Aug 7 2008, 11:33 AM) Which I will be doing for the Mac. See, on the Mac, the shortcut is cmd+shift+space because cmd+space is the shortcut for spotlight. But requiring a double modifier is a real pain for this accelerator. Why didn'
  9. QUOTE (silmaril @ Aug 7 2008, 01:49 AM) The Report Type enum is required in LabVIEW 8.6, but the enum contents are the same whether or not you have the toolkit installed. So this issue should no longer occur when using a VI on two different systems, one with the toolkit installed and one without. -D
  10. QUOTE (Antoine Châlons @ Aug 6 2008, 11:58 PM) The default key combination is Ctrl-Space (Cmd-Shift-Space on Mac), but you can customize it in Tools > Options > Menu Shortcuts to be something else if you want. -D
  11. QUOTE (normandinf @ Aug 6 2008, 04:15 PM) My week was very heavily front-loaded due to all the prep work for the Tuesday keynote. I've still got stuff going on today and tomorrow, but the hardest stuff is over (for me, anyway). -D
  12. QUOTE (jdunham @ Aug 6 2008, 03:38 PM) Please do...I just tried the behavior you described in both 8.5 and 8.6 and I'm not seeing it. -D
  13. Here's a VI that will give the top-down inheritance hierarchy of a .lvclass file. It reads the linkage information from the file on disk, so there's no VI Server or scripting code (although I do use a private method to get the linkage info, so the VI is password-protected). I tested the VI in 8.5 and 8.6 and it seems to work. Hope this helps, -D
  14. QUOTE (b_subhasis @ Aug 6 2008, 02:26 AM) I'm glad to see http://zone.ni.com/devzone/cda/tut/p/id/7423' target="_blank">Quick Drop made your list. You mention in your document that you can drop the object by pressing 'Enter'. That is true, however, there's another, even faster way to use Quick Drop. After you have typed the shortcut or object name (or typed enough of it that auto-complete has finished it for you), if you click in the VI to dismiss Quick Drop, it will drop the object you selected where you clicked. No 'Enter' necessary, and you can skip the step of having the obje
  15. QUOTE (jdunham @ Aug 6 2008, 02:28 PM) MenuLaunchApp should always give the application instance that owns the VI from which you launched the Tools menu option. If you're seeing different behavior, it might be a bug. Can you give me specific steps to reproduce the problem? I'm not seeing it here... -D
  16. QUOTE (crelf @ Aug 5 2008, 11:05 PM) I honestly don't know what we're going to do yet...one thing I was thinking was that we'd keep the Report Gen instance information within the class data, as opposed to using a separate shift register database (as we're doing now). Also, I think the shift register database approach is only used with the HTML report type, since all the other reports (Standard, Excel, and Word) use references (based on their ActiveX roots). So splitting the class wire for Standard, Word, or Excel reports wouldn't create a "new" report in that case. We're effectively mim
  17. QUOTE (crelf @ Aug 5 2008, 11:43 AM) Yup...if we made it so that when you split the wire you had two different reports, then that would make the toolkit behave differently now than it did in past versions. The last time I checked, LabVIEW users generally like for VIs to function the same after upgrading. -D
  18. QUOTE (Norm Kirchner @ Aug 3 2008, 12:01 PM) I made that video about a month ago. Since then, I have gotten into the habit of dropping constants with Quick Drop (I have 'nc' as a shortcut for Numeric Constant) instead of creating them from the right-click menus. So I probably could have shaved off about 5 seconds on that VI time if I had been doing that. I agree that going into the right-click menu to drop a constant is slower than it should be. -D
  19. QUOTE (GraemeJ @ Aug 2 2008, 07:13 PM) Typically your entire application resides in a folder structure of some sort on disk. Can you just create a new VI Analyzer task (as opposed to using the "Analyze this VI" functionality) and add the folder(s) containing your app, then run the Enabled Debugging test over the entire folder? -D
  20. QUOTE (crelf @ Aug 2 2008, 04:22 PM) He's worked in LabVIEW R&D for longer than I have, so I'll let you guys figure out who he is. -D
  21. QUOTE (deirdre @ Aug 2 2008, 03:56 PM) I'm glad I visit LAVA regularly...otherwise I wouldn't have known that I was supposed to be in a coding contest on Thursday... -D P.S. - If y'all want to know what you're up against, there's a video of me writing a VI in LabVIEW 8.6 on the http://zone.ni.com/devzone/cda/tut/p/id/7423' target="_blank">Quick Drop page.
  22. QUOTE (crelf @ Aug 2 2008, 11:12 AM) I don't own Report Generation anymore. The guy who does, however, has the same initials as me, and he sits right next to me... Even crazier is the fact that I participated in the code review, but that was his comment, not mine... Oh, and as for the object repository, that's a holdover from the original design. The user-facing API became class-based, but some of the underlying code stayed the same. Look for the Report Gen codebase to become more OOPish in future releases. -D
  23. The University of Texas at Austin The Georgia Institute of Technology -D
  24. This thread makes me think of two things. First, make sure y'all submit suggestions for any LabVIEW features you want to the Product Suggestion Center. I promise we do actually read every single one that comes in, and the more similar ones we get from different people, the higher the chance it will become a feature someday. Second, perhaps this thread would be more effective if it were a LAVA Wiki entry? I envision a list of feature requests on a Wiki page, and it can be updated after every LabVIEW release by moving things from the "requested" list into the "hey, it's a feature now!" list.
  25. Ok, at the risk of seemingly hopelessly un-hip, is there some sort of pop culture reference I'm missing with this? I'm all about funny web phenomenons, but I'm completely lost here... -D P.S. - Surely I'm speaking for some other LAVAers out there who didn't "get" this???
×
×
  • Create New...

Important Information

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