Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. QUOTE (Aristos Queue @ Feb 12 2009, 05:34 PM) I believe this statement will be my motivation to actually write the blog article on LabVIEW Object-Oriented Programming that has been brewing in the back of my brain for months now. You have been warned... -D
  2. QUOTE (ACS @ Feb 12 2009, 11:19 AM) Lest someone read this and get confused, I should point out that LV Class programming is not required on the CLA. You can certainly use them if you want, but they are not a required component of your architecture. I did not use LV Classes in my code for the CLA (and I passed). -D
  3. QUOTE (Darren @ Feb 5 2009, 09:37 PM) I just finished the article on my blog about preparing for the CLA. See http://labviewartisan.blogspot.com/2009/02/labview-certification-preparing-for-cla.html' rel='nofollow' target="_blank">here. -D
  4. QUOTE (Michael Aivaliotis @ Feb 5 2009, 06:37 PM) Thanks for the shout-out, Mike. And congrats on passing the CLD, Mark! I plan on posting an article on my blog soon about preparing for the CLA...stay tuned! -D
  5. Darren

    My CLD plan

    I posted my suggestions for preparing for the CLD on my blog. See here. -D
  6. QUOTE (Michael Aivaliotis @ Feb 4 2009, 02:26 PM) Quad core @2.4 GHz, 4 GB of RAM. I don't think that counts as an old slow machine, does it? I don't have any shoes in my Start Menu...maybe that was the problem? -D
  7. I just got a new Vista machine at work a few weeks ago. One of the first things I did was change the system theme to "Classic" so it looks like the old Windows 2000 look. All the font sizes look normal to me, I'm not seeing any bent wires in old code or larger-than-usual comments. I changed the theme just because I figured the fancy Vista shinyness probably wasn't worth any performance hits I knew I'd encounter (for example, the Start menu took a second to appear with the default Vista theme, but appears instantly with the Classic theme). From what y'all have said, it looks like the font i
  8. Q: What are you if you are a naked secret agent answering a 40-question multiple choice exam about LabVIEW? A: The Man from U.N.C.L.A.D. -D
  9. QUOTE (Aristos Queue @ Jan 30 2009, 06:45 PM) It seems like worldwide adoption of LabVIEW as a general purpose language would mean nothing but good things for NI. But then again, I'm not a marketer either... -D
  10. QUOTE (crelf @ Jan 29 2009, 05:51 PM) I tried describing Twitter to AQ at either the Norm lunch or the JKI lunch (can't remember which...they were both at the same place, with some of the same people) and I got confused looks and rolled eyes. I'm guessing we won't see him on there anytime soon... -D
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
  • Create New...

Important Information

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