Jump to content

Darren

NI
  • Content Count

    560
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by Darren

  1. Ok, I got a response on the truthiness of what I said: "That is basically true. Some toolkits (SIT, for example) have some shared components that install outside of the LabVIEW folder that might be upgraded and affected. But in general Toolkits and Modules on the DVD only install to 8.6 and won't affect old versions or newer versions. Not all modules and toolkits are on the DVD though, so your mileage may vary for those. As for drivers, the ones on the August 2008 Driver DVD support LabVIEW 7.1.x, 8.2.x, 8.5.x and 8.6." -D
  2. QUOTE (neB @ Aug 12 2008, 10:13 AM) I'm not as familiar with the installers for drivers and modules, but I can almost guarantee that with drivers, the new install will uninstall old stuff just like it always did. I'm not sure about modules. But you should be good with toolkits (VI Analyzer, Report Gen, Internet, Database, etc.) If I had to guess, I'd say modules are probably good, because I think every installer on the LabVIEW Platform DVD will now adhere to the "install only to the current LabVIEW version and don't mess with other stuff" rule that the toolkit installers now abide by. I'll make sure the right NI people see this post so they can correct me if I'm wrong. -D
  3. QUOTE (Ton @ Aug 12 2008, 12:33 AM) Starting with LabVIEW 8.6 and moving forward, a LabVIEW/toolkits install will no longer affect the installs of previous toolkits. So yes, your older toolkits are safe when installing LabVIEW 8.6. -D
  4. QUOTE (ragglefrock @ Aug 11 2008, 01:59 PM) I use SCC in the LabVIEW project, but our server is pretty snappy. I'm not too familiar with LabVIEW launch time speed issues, but I think I've heard people blame slow SCC servers and weird licensing network problems for slow LabVIEW launches in the past. -D
  5. 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 is your first time running LabVIEW after installing it (or after rebooting your machine). Also, if I let LabVIEW sit for a minute after launch, and I'm using "Load Palettes in Background", the first Quick Drop launch only takes about 1 1/2 seconds, as opposed to 4. -D
  6. 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
  7. 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
  8. 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 shortcut key combination). -D
  9. 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
  10. 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 the mouse when I'm using Quick Drop. -D
  11. 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 screwing up my auto-complete in the future. But I digress... There are three ways to drop an object once Quick Drop is open. Let's say I want to drop an "Add" function: 1. Press Ctrl-Space. Type "add". Press Enter. Quick Drop disappears, and an Add function appears on my cursor. Drop the Add function wherever I want it in my VI. 2. Press Ctrl-Space. Type "add". Double-click on the "Add" function that appears in the name match list below. Quick Drop disappears and an Add function appears on my cursor. Drop the Add function wherever I want it in my VI. 3. Press Ctrl-Space. Type "add". Click in the VI where I want the Add to be. Quick Drop disappears, and the Add is already dropped in the diagram where I clicked. Method #3 is what I use 99% of the time I'm using Quick Drop. I like to call it "Super Quick Drop". I will be posting a nugget on the http://forums.ni.com/' target="_blank">NI Discussion Forums in the near future where I expound on pretty much everything there is to know about Quick Drop. Stay tuned... -D
  12. 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't we make it ctrl+space on the Mac? I know cmd is our normal modifier, but the ctrl key is available in this case and it seems like a more reasonable choice than adding the shift key. Hmm...you know a message board thread has gotten out of hand when you have to reply two different times to address two entirely different messages in the same thread... If I recall correctly, the Ctrl key cannot currently be assigned to shortcuts in Tools > Options > Menu Shortcuts on the Mac. We didn't have the resources in 8.6 to add this ability, so we did the same thing the Context Help window does on Mac...we used Cmd-Shift as the modifier since the Cmd modifier was already claimed by something in the OS. -D P.S. - What shortcut are you planning on using? Tell me if whatever you choose works well, and I'll start recommending it as an alternative to Mac users.
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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 object on your cursor. I like to call this method 'Super Quick Drop'. -D
  19. 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
  20. 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 mimicking that behavior with the shift register database for HTML reports. QUOTE (crelf @ Aug 5 2008, 11:05 PM) PS: I appreciate you guys taking time out during NI-Week to keep posting on the forums. I know how crazy-busy everyone at NI is I'm very interested to hear what you guys have to say about LabVIEW 8.6, so I'm trying to check in frequently. -D
  21. 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
  22. 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
  23. Darren

    Debugging Off

    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
  24. 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
  25. 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.
×
×
  • Create New...

Important Information

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