Darren

QUOTE (normandinf @ Aug 6 2008, 04:15 PM) My week was very heavily front-loaded due to all the prep work for the Tuesday keynote. I've still got stuff going on today and tomorrow, but the hardest stuff is over (for me, anyway). -D

QUOTE (jdunham @ Aug 6 2008, 03:38 PM) Please do...I just tried the behavior you described in both 8.5 and 8.6 and I'm not seeing it. -D

Here's a VI that will give the top-down inheritance hierarchy of a .lvclass file. It reads the linkage information from the file on disk, so there's no VI Server or scripting code (although I do use a private method to get the linkage info, so the VI is password-protected). I tested the VI in 8.5 and 8.6 and it seems to work. Hope this helps, -D

QUOTE (b_subhasis @ Aug 6 2008, 02:26 AM) I'm glad to see http://zone.ni.com/devzone/cda/tut/p/id/7423' target="_blank">Quick Drop made your list. You mention in your document that you can drop the object by pressing 'Enter'. That is true, however, there's another, even faster way to use Quick Drop. After you have typed the shortcut or object name (or typed enough of it that auto-complete has finished it for you), if you click in the VI to dismiss Quick Drop, it will drop the object you selected where you clicked. No 'Enter' necessary, and you can skip the step of having the object on your cursor. I like to call this method 'Super Quick Drop'. -D

QUOTE (jdunham @ Aug 6 2008, 02:28 PM) MenuLaunchApp should always give the application instance that owns the VI from which you launched the Tools menu option. If you're seeing different behavior, it might be a bug. Can you give me specific steps to reproduce the problem? I'm not seeing it here... -D

QUOTE (crelf @ Aug 5 2008, 11:05 PM) I honestly don't know what we're going to do yet...one thing I was thinking was that we'd keep the Report Gen instance information within the class data, as opposed to using a separate shift register database (as we're doing now). Also, I think the shift register database approach is only used with the HTML report type, since all the other reports (Standard, Excel, and Word) use references (based on their ActiveX roots). So splitting the class wire for Standard, Word, or Excel reports wouldn't create a "new" report in that case. We're effectively mimicking that behavior with the shift register database for HTML reports. QUOTE (crelf @ Aug 5 2008, 11:05 PM) PS: I appreciate you guys taking time out during NI-Week to keep posting on the forums. I know how crazy-busy everyone at NI is I'm very interested to hear what you guys have to say about LabVIEW 8.6, so I'm trying to check in frequently. -D

QUOTE (crelf @ Aug 5 2008, 11:43 AM) Yup...if we made it so that when you split the wire you had two different reports, then that would make the toolkit behave differently now than it did in past versions. The last time I checked, LabVIEW users generally like for VIs to function the same after upgrading. -D

QUOTE (Norm Kirchner @ Aug 3 2008, 12:01 PM) I made that video about a month ago. Since then, I have gotten into the habit of dropping constants with Quick Drop (I have 'nc' as a shortcut for Numeric Constant) instead of creating them from the right-click menus. So I probably could have shaved off about 5 seconds on that VI time if I had been doing that. I agree that going into the right-click menu to drop a constant is slower than it should be. -D

QUOTE (GraemeJ @ Aug 2 2008, 07:13 PM) Typically your entire application resides in a folder structure of some sort on disk. Can you just create a new VI Analyzer task (as opposed to using the "Analyze this VI" functionality) and add the folder(s) containing your app, then run the Enabled Debugging test over the entire folder? -D

QUOTE (crelf @ Aug 2 2008, 04:22 PM) He's worked in LabVIEW R&D for longer than I have, so I'll let you guys figure out who he is. -D

QUOTE (deirdre @ Aug 2 2008, 03:56 PM) I'm glad I visit LAVA regularly...otherwise I wouldn't have known that I was supposed to be in a coding contest on Thursday... -D P.S. - If y'all want to know what you're up against, there's a video of me writing a VI in LabVIEW 8.6 on the http://zone.ni.com/devzone/cda/tut/p/id/7423' target="_blank">Quick Drop page.

QUOTE (crelf @ Aug 2 2008, 11:12 AM) I don't own Report Generation anymore. The guy who does, however, has the same initials as me, and he sits right next to me... Even crazier is the fact that I participated in the code review, but that was his comment, not mine... Oh, and as for the object repository, that's a holdover from the original design. The user-facing API became class-based, but some of the underlying code stayed the same. Look for the Report Gen codebase to become more OOPish in future releases. -D

The University of Texas at Austin The Georgia Institute of Technology -D

This thread makes me think of two things. First, make sure y'all submit suggestions for any LabVIEW features you want to the Product Suggestion Center. I promise we do actually read every single one that comes in, and the more similar ones we get from different people, the higher the chance it will become a feature someday. Second, perhaps this thread would be more effective if it were a LAVA Wiki entry? I envision a list of feature requests on a Wiki page, and it can be updated after every LabVIEW release by moving things from the "requested" list into the "hey, it's a feature now!" list. -D

Ok, at the risk of seemingly hopelessly un-hip, is there some sort of pop culture reference I'm missing with this? I'm all about funny web phenomenons, but I'm completely lost here... -D P.S. - Surely I'm speaking for some other LAVAers out there who didn't "get" this???

How strange...yesterday, for the first time in my life, I attempted to wire an array to Initialize Array (and got a broken wire, and wondered why it wasn't allowed). Then I discovered this thread today... -D

QUOTE (Aristos Queue @ Jun 17 2008, 04:28 PM) Yup, and as many of you may recall, LabVIEW 4.20 was after your munchies... -D

I really dislike the palettes too...especially since everything was rearranged in 8.0. If only someone could do something about them! I mean, if somebody with my distaste for the palettes happened to work in LabVIEW R&D, then he could add a feature in the next LabVIEW release that allowed me to write VIs faster than ever before, without having to ever bring up the palettes again. Man, that would be so great! Oh well, maybe someday. Someday... -D

QUOTE (Aristos Queue @ Apr 29 2008, 01:30 PM) How are they faster than Ctrl-X/C/V? The X, C, and V keys are all very close to the left Ctrl key and typable with the left hand only. -D

Check out the attached VI. It overrides those not-so-pretty tree symbols with better looking ones (specifically, the icons used in the Project Window). After you run this VI on your tree, whenever you add new items programmatically, if you set their symbol index to be one of the old-skool symbols, you'll get the nicer looking one instead. This should work in LabVIEW 8.0 and later. -D P.S. - To turn off the hierarchy lines on the tree, right-click the tree and uncheck Visible Items > Hierarchy Lines.

QUOTE (Aristos Queue @ Apr 4 2008, 02:34 PM) When I wrote a LV Class-based app a while back, I tried to make the wire colors match the default banner colors. I used a darker, mustardy yellow with the yellow-bannered classes to make the wires look nicer on the diagram. I think it would be good to try to match up the wire colors to the banner colors by default. I would also like it if we cycled through more than 6 colors. -D

Now that 8.5.1 is out, you should add it to the LV Version Used rings on our profile page. -D

QUOTE (Val Brown @ Apr 4 2008, 01:46 PM) I don't think any discussion of beta software (including the topic of having been a beta tester) is allowed outside the private NI channels. -D

QUOTE (orko @ Apr 2 2008, 08:31 AM) I actually used the http://en.wikipedia.org/wiki/Etch_A_Sketch#Etch_A_Sketch_Animator' rel='nofollow' target="_blank">Etch-A-Sketch Animator when I was a kid, which allowed you to erase... -D

QUOTE (Phillip Brooks @ Apr 1 2008, 07:06 AM) This functionality is already supported in the Wire Bends test of the VI Analyzer. http://lavag.org/old_files/monthly_04_2008/post-4441-1207072727.png' target="_blank"> Hope this helps, -D