Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. QUOTE (JiMM @ Aug 31 2008, 11:00 AM) Can you qualify that statement? I'm (obviously) biased, but I feel the LabVIEW documentation is some of the best I've ever encountered in the software world. I didn't immediately jump on the project bandwagon in 8.0, but when I eventually did, I found its use and documentation pretty straightforward. If you had problems, with the project documentation or anything else, please report it on the http://forums.ni.com' target="_blank">NI Forums so our Applications Engineers can file bug reports (CARs) so we can make the documentation as good as possib
  2. QUOTE (neB @ Aug 29 2008, 11:00 AM) The "authorities" have been notified of your concern. -D Edit: The authorities say that even if we remove a setting from Tools > Options, it is highly unlikely that we would remove it as an INI token as well.
  3. I understand your concern, but if we just receive a bunch of INI files full of the same tokens (because everybody stuffed their files with tokens everybody else uses), the study provides NI with no useful information, and this benefits no one. So do what you want, but I feel that the best way for this study to benefit the LabVIEW community would be for everybody to submit the INI files they actually use. -D
  4. Instead of submitting an artificial INI file, the study would probably be more effective if you submitted your actual INI file, then encouraged everybody (who would have been supplying you with INI tokens you don't use) to submit theirs as well. -D
  5. Looks like I wasn't the only guy who thought Ctrl-Space was a useful key combo... -D
  6. There's a text file containing shortcuts on the Quick Drop webpage. You can copy the two INI tokens in that text file into your LabVIEW.ini file and you'll be good to go. For convenience, I've attached the file here...actually, this is my latest list of shortcuts, so it may have a few more than the one on the webpage. -D P.S. - You'll notice that almost all of my shortcuts can be typed with the left hand only (I'm right handed). Thus, if I type a shortcut, and then click in the VI to dismiss Quick Drop and automatically drop the item, I never have to move my left hand from the keyboard, a
  7. QUOTE (jcarmody @ Aug 27 2008, 05:08 AM) Click the Shortcuts button in the Quick Drop dialog. http://lavag.org/old_files/monthly_08_2008/post-4441-1219849257.png' target="_blank"> -D
  8. QUOTE (Norm Kirchner @ Aug 26 2008, 10:30 AM) I have a shortcut ('sav') for Select a VI. So I Ctrl-Space, 'sav', click in the VI, and I have a file dialog to pick a VI from disk. http://www.youtube.com/watch?v=sRA0bRtsuqA' rel='nofollow' target="_blank">Total beans. -D
  9. Darren

    Tip strip

    QUOTE (ASTDan @ Aug 22 2008, 10:29 AM) I don't know how to control the tip strip from an OS level, but I do have a colleague who didn't like the way control/indicator tip strips behaved, so he made his own. It's a 2D-style string control with a black border and pale yellow background that he shows/hides and programmatically moves around as needed, and looks pretty darn close to what a real tip strip looks like. The only limitation I remember seeing in his implementation was that (obviously) his tip strip couldn't go beyond the bounds of the front panel window, whereas a native tip strip
  10. QUOTE (Michael_Aivaliotis @ Aug 22 2008, 03:08 AM) Let the record show, your honor (yes, I'm assuming Michael is the judge in this case), that I was not defending the appearance of the 3-button dialog VI, I was merely defending the use of a Flat Sequence in a UI VI. AQ made a perfect argument regarding Flat Sequence usage, and I was affirming that argument. -D P.S. - In his defense, though, given the huge amount of initialization required in the 3-button dialog VI, I'm curious how others would design it that it would look so different. Is the issue purely one of modularization? Would
  11. QUOTE (normandinf @ Aug 22 2008, 08:11 AM) In LabVIEW 8.6 there is a small set of VIs that deal with VI and object tags. They are located at [LabVIEW 8.6]\vi.lib\UserTags. Let me know if you have any feedback on them. -D
  12. QUOTE (Aristos Queue @ Aug 21 2008, 05:17 PM) Not so fast...before the defense rests, you should call your first witness, Darren, who has advocated Flat Sequences as a perfectly legitimate UI programming structure for many years (when was the 7.0 release?), for the very reasons you have cited. -D P.S. - Stacked Sequences, however, are pure evil. Just want to make sure there's no question on that.
  13. QUOTE (martin@aerodynamics @ Aug 20 2008, 07:03 AM) That's correct...it requires the released version of LabVIEW 8.6. -D
  14. QUOTE (crelf @ Aug 19 2008, 02:55 PM) Under the hood is a VI that runs on the target that implements the ladder logic, but the user doesn't have access to that VI. He can, however, add VIs to the rungs of his ladder diagram, and those VIs can do whatever he wants. -D
  15. QUOTE (rayodyne @ Aug 18 2008, 12:42 PM) Thanks for the clarification. Unfortunately, there is currently no way to export the Error List contents. It does seem like a useful suggestion, though...I recommend you submit this idea to the http://digital.ni.com/applications/psc.nsf/default?OpenForm' target="_blank">Product Suggestion Center. -D P.S. - I'm also curious about the broken VIs...were they unbroken in 8.5, but broken in 8.6? What specifically is wrong on their diagrams? Are there toolkits you have installed in 8.5 that you don't have installed in 8.6?
  16. QUOTE (Antoine Châlons @ Aug 18 2008, 01:26 AM) As far as I can tell, it's not in 8.5 or 8.6. There is currently a CAR on the issue (CAR# 113669) that is being investigated by LabVIEW R&D. -D
  17. QUOTE (rayodyne @ Aug 17 2008, 04:17 PM) What "Error List" are you talking about? Can you attach a screenshot? -D
  18. Darren


    QUOTE (PJM_labview @ Aug 16 2008, 11:01 AM) Awesome! I didn't realize people took pictures. Yeah, that was the robot that the Aggie grad students made. -D
  19. Darren


    QUOTE (Tom Bress @ Aug 15 2008, 11:01 AM) I play them with the Wiimote...if you eliminate the lag issue as I discussed above, the Wiimote has a surprisingly natural feel when playing the old games. I don't own the Wii classic controller...I have 4 Wiimotes and 2 Nunchuks. At some point I'll probably get a game that requires 4 players to have 4 Nunchuks, but so far, the hardware I have has sufficed. -D
  20. Darren


    QUOTE (Tom Bress @ Aug 15 2008, 09:08 AM) In no particular order, here are my "Wii Tips": Super Mario Galaxy is one of the best video games I've ever played in my life. If you were a fan of Mario games in the past, this one will completely blow you out of the water. My kids and I were totally addicted to it for the ~2 months it took us to beat the game (twice). Big Brain Academy is a really fun puzzle game. You compete either against 1 other person or you can have teams compete to solve logic/numeric/analysis/observation puzzles as quickly as possible. You definitely want to get Wi
  21. 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
  22. 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.
  23. 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
  24. 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
  25. 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
  • Create New...

Important Information

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