Darren

QUOTE (Gary Rubin @ Mar 5 2009, 06:48 AM) My Zs have a distinct angular upper corner...my 2s have a curved upper corner. They look pretty much exactly like 'Z' and '2'. Thread hijack ftw! -D

QUOTE (crelf @ Mar 4 2009, 09:23 PM) I say 'zee', and I don't draw lines through the middle of my Zs or 7s either. -D

QUOTE (dannyt @ Mar 3 2009, 02:33 AM) Last I checked, my address is in Austin, TX, USA. http://www3.telus.net/linguisticsissues/BritishCanadianAmerican.htm' rel='nofollow' target="_blank">We use Zs here. -D

Looking at the diagram of the Conditional Error Probe (vi.lib\_probes\default\ConditionalErrorProbe.vi), it looks like either the General Error Handler CORE.vi or that mysterious Conditional Disable Structure is to blame. -D

QUOTE (jasonw @ Feb 27 2009, 08:20 AM) If you chant 3 times at 8:20 AM, no, I'm afraid Darren won't come answer this. I'm not what you would call a "morning person"...in fact, my pre-10AM response to this message is quite an anomaly. Kids woke up earlier than usual this morning... Anyway, when I developed Quick Drop, I wanted to make sure I could drop items without having to move my hands from their normal "left hand: keyboard, right hand: mouse" position. So I added the ability to click and dismiss Quick Drop to immediately drop the item, as Ben pointed out. This is called Super Quick Drop, and it's one of several advanced Quick Drop tips I've outlined http://forums.ni.com/ni/board/message?board.id=170&thread.id=361708' target="_blank">here. -D

QUOTE (crelf @ Feb 24 2009, 05:20 PM) Oh crap, that was hilarious. Louis CK is great, I've watched some of his stand-up. Too bad his HBO show tanked. -D

Why are you building your tool into an EXE? If it is to simply call the tool as a scheduled task in Windows, you can always schedule a task that launches LabVIEW.exe and specifies a VI to run as a command line parameter. -D

The VI Analyzer VIs do not work in a built executable. There is certain internal functionality used by the VI Analyzer that is not supported in the LabVIEW Runtime Engine. I was surprised to see that we do not mention anywhere in the VI Analyzer documentation that the VIs are not supported in a built EXE. I have filed a CAR against the documentation (CAR# 147643) that we add this information. -D

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

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

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

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

I posted my suggestions for preparing for the CLD on my blog. See here. -D

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

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 issues were another good reason to go with classic. -D

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

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

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

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

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

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

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

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

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

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