Jump to content

Darren

NI
  • Content Count

    582
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by Darren

  1. Your VI was saved with its block diagram removed. You need to find out if there's a backup of the VI anywhere that still has the diagram...otherwise, you're stuck with it. Also note that you can't use a diagram-less VI in any LabVIEW version other than the one it was last saved in (i.e. the version used to remove its diagram). Good luck, -D
  2. QUOTE (crelf @ Oct 28 2008, 07:40 PM) I assume that's it...I've heard of the OpenG Builder but I would have had trouble with the "OGB" acronym just reading the initial unedited post. -D
  3. 2.63 on my first try...I think that explains why my VI wires are so straight. -D
  4. QUOTE (ancle @ Oct 2 2008, 10:05 PM) See http://forums.lavag.org/-t11805.html&view=findpost&p=51007' target="_blank">this post, where I attached a file with my shortcuts. -D
  5. This problem always intrigued me, but I was never able to come up with a solution. In case anybody is interested, I posted the Round Robin problem on the LabVIEW Puzzles thread on the NI Forums, and one of the NI Forums members named ShotSimon was able to come up with a solution. See here. -D
  6. I agree...it seems to me we should turn off this setting for subVIs in a built EXE. I made sure the App Builder team is aware of this thread. For now, you can use the attached VI Analyzer Test (saved in 8.6) to detect this situation in your VIs before you build an EXE. Place this LLB in [LabVIEW Data]\VI Analyzer Tests, then launch Tools > VI Analyzer > Analyze VIs and the SubVI Suspend When Called test will be one of the tests you can run. Note that in LabVIEW 8.6, you do not need to have the VI Analyzer Toolkit installed in order to run tests...the UI and Engine for the VI Analyzer
  7. QUOTE (AnalogKid2DigitalMan @ Sep 3 2008, 04:14 PM) My son (who was 3 at the time) started calling PT Cruisers 'slugs' because "they kinda look like slug bugs". So we call slug bugs, slugs, cons, and Ds. 'Con' is convertible. 'D' is Durango, which is what I drive. -D (for 'Darren', not 'Durango')
  8. Darren

    Wii

    QUOTE (JiMM @ Sep 3 2008, 06:39 PM) I just bought Mario Kart Wii a few weeks ago. For anyone who was a world-class expert at Mario Kart for the N64, you may find some of the differences beween N64 and Wii to be a bit annoying. For example, you can lose powerups that you're holding onto if you fall off a ledge, get hit by an opponent with star power, etc. Also, power-sliding (now called 'mini-turbo') has lost a lot of its subtlety, which is a shame for those of us who perfected it on N64. They made the off-road areas (grass, mud, etc.) slow down your vehicle a LOT more than in N64...for
  9. QUOTE (Michael_Aivaliotis @ Sep 1 2008, 02:16 AM) I was primarily responding to the "as usual" comment. Anyway, my favorite use of the project is the built-in SCC. Being prompted to check out a file that I don't have checked out whenever I start trying to edit it is really handy. -D
  10. 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
  11. 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.
  12. 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
  13. 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
  14. Looks like I wasn't the only guy who thought Ctrl-Space was a useful key combo... -D
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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.
  22. QUOTE (martin@aerodynamics @ Aug 20 2008, 07:03 AM) That's correct...it requires the released version of LabVIEW 8.6. -D
  23. 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
  24. 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?
  25. 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
×
×
  • Create New...

Important Information

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