Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. QUOTE (Ton @ Jan 27 2009, 11:14 PM) I tried those, couldn't get either of them to fire on a panel window move. -D
  2. There is currently no event-based way to determine if a VI's panel is moved. The previous two suggestions (your suggest of polling, and Aristos' suggestion of Windows DLL calls) are the only options. I have used the polling technique to link VI windows before...it's rather choppy. If you end up getting a decent implementation of the Windows calls working, I'd like to see it. -D
  3. QUOTE (crelf @ Jan 23 2009, 05:47 PM) Hopefully everybody noticed that I wrote that VI 10 years ago. I was in LabVIEW Basics class, and it was my very first LabVIEW app. I assure you the framework I wrote during the CLA last month was much cleaner. -D
  4. QUOTE (PJM_labview @ Jan 16 2009, 05:25 PM) In LabVIEW 8.6 there is a private event called "Shortcut Menu Dismissed". There's also the equally-handy "Operate Menu Dismissed" that fires when you dismiss the operate menu of a ring, enum, etc. -D
  5. QUOTE (PJM_labview @ Jan 16 2009, 05:25 PM) In LabVIEW 8.6 there is a private event called "Shortcut Menu Dismissed". There's also the equally-handy "Operate Menu Dismissed" that fires when you dismiss the operate menu of a ring, enum, etc. -D
  6. QUOTE (Phillip Brooks @ Jan 9 2009, 12:42 PM) I don't know of a way to exactly reproduce the Context Help window contents based on VI path only, but the private App methods "Get VI.Description", "Get VI.Title", and "Get VI.Icon" can get you pretty close. All of those methods take a file path input and do not require opening a VI reference. -D
  7. I use dual non-wide CRTs, both at 1152x864. Tried to switch to 1280x1024 the other day, but almost got a headache from the squinting, so I switched back. Laptop at home is wide 1280x800, but I rarely do serious programming at home. -D
  8. Sorry, Rolf. I was thinking only of the toolkits owned by the LabVIEW team (Database, Report Gen, VI Analyzer, Internet, etc. etc.) when I made that statement. I didn't think of hardware-related toolkits. If you haven't already, please report this bug on the NI Forums so the AEs can investigate. -D
  9. My first thought was to solve it like jdunham suggested...it would be interesting to compare the performance of the techniques...I wonder if there's a way to get rid of the memory allocation on the second indexing tunnel? -D
  10. QUOTE (Justin Goeres @ Dec 6 2008, 08:40 AM) Popping up a dialog and requiring user interaction doesn't seem like too much of an improvement over Michael's Find/Replace trick (and I believe his trick is undoable). I was suggesting that we do automatic relinks only in cases of changed connector pane, with no renamed terminals (and the VI still residing in the same place on disk). Are y'all not comfortable with an automatic relink in this scenario? I think a change like this would primarily benefit people in Michael's scenario, or people who distribute VI-based APIs and need to add connec
  11. QUOTE (Michael_Aivaliotis @ Dec 5 2008, 09:36 PM) That is a nifty trick that I did not know about. Good find. I'm pretty sure I would have attempted to solve this with scripting if I had 675 instances to fix... Along these lines, I'd like to know how you guys would feel about LabVIEW doing the relinking automatically in some cases. There are a few reasons that the relink is currently manual...for instance, if there are several identical data types on the conpane, and in addition to changing the pattern, you also rearranged (and renamed) some of the terminals, the relink might not wire
  12. I ran into this exact issue a while back...I posted the CAR number I filed on the corresponding thread on the NI forums. -D
  13. QUOTE (jdunham @ Nov 21 2008, 12:51 PM) We've received this feature request before...we're looking into adding functionality along these lines in a future LabVIEW version. QUOTE (jdunham @ Nov 21 2008, 12:51 PM) It works great for opening VIs, but often it would be cool to have the VI it finds available for dropping on a diagram. PJM's suggestion about replacing an existing palette VI with your VI is intriguing, but it seems to me you might have linking issues (like VI search dialogs) when dropping a VI that normally resides in one location on disk from a completely different locatio
  14. QUOTE (jdunham @ Nov 19 2008, 08:19 PM) How are you specifying which VI you want to drop off disk? If it's with a File Dialog, you can just use Quick Drop to "Select a VI...". In fact, I have a shortcut ('sav') for Select a VI to make it even faster. -D
  15. QUOTE (jdunham @ Nov 20 2008, 02:14 PM) You can use scripting to drop a VI from disk (the New VI Object function has a path input), but there is no easy way of putting an arbitrary VI of your choosing *on the cursor*. The Drop Ctrl or Func method will only take an object name (as a string), and that object has to be on the palettes. The only way I can think of (and this is very kludgey) is to programmatically add the VI in question to the palettes with the Palette API (maybe to a dummy user.lib subpalette?), programmatically refresh the palettes, then use Drop Ctrl or Func (or Quick Drop
  16. 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
  17. 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
  18. 2.63 on my first try...I think that explains why my VI wires are so straight. -D
  19. 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
  20. 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
  21. 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
  22. 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')
  23. Darren


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

Important Information

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