Darren

"Top 10 letters Darren is least likely to ever have to write"

Damnit, Stephen, stop showing me expensive things that I want. Thankfully, Cubelets are so over-the-top expensive that the practicality of putting food on the table immediately overrides my normal impulse of reaching for the credit card. Now, if they were about half that price, I don't know if I could control myself...

I've only ever used Class Operator in conjunction with the Traverse method. You set an operator VI that runs whenever the Traverse method finds an object matching the class name you specify. For my Traverse VIs, the operator VI is very simple...it just adds the found object's reference to an array. I know other people have written their own traversal algorithms that have the operator VI do a lot more stuff when it finds the object.

The following VI is available in LabVIEW 2010 and later...you should be able to dig through it to find out everything I know about the Class Operator and Traverse methods:

<LabVIEW>\vi.lib\Utility\traverseref.llb\Traverse for GObjects.vi

Can't wait to hear more of Poet Laureate Nattinger's limericks...

Oh man, my creative juices are spent after writing (and memorizing) those limericks last year.

Please...don't make me do it again! (insert preemptive TWSS here)

I currently have 3 monitors (two up top, one in the center below). Hope to get a 4th soon.

I haven't seen this in 2011. But in the past, I have seen major bog-downs in text search for projects containing lots of picture control stuff, since (I think) the string search actually parses picture data as string data. Do the VIs in memory that you're searching have a lot of picture control stuff going on?

I had this issue in the Quick Drop window. And for reasons I can't remember now, I wasn't able to use a system combo box. So my solution was to have a frame decoration, with the same color as the panel, that I position exactly where that ugly black box would be. And the decoration is higher up in the panel order than the combo box. So when I assign key focus to the combo box, you don't see the ugly black border because the panel-colored decoration is above it. I also have to resize this decoration on a panel size, to ensure it's always surrounding the combo box at exactly the right size.

Programming UIs in LabVIEW is fun!

That onesie rules!

I'll be there. Thanks for organizing this, Jeremy.

Here's a VI that tries to do what File > Save All (this Project) does. We are planning on shipping this VI with LabVIEW 2012.

Save All This Project (2011).vi

Ok, then maybe picktime.vi is called elsewhere, and that dialog that comes up from the Timestamp is a built-in (i.e. not a VI) dialog? If that's the case, then yeah, short of modifying the application font settings like mike5 suggested, I don't have any other ideas.

If you're referring to the dialog I think you're referring to, it is a VI-based dialog and can be found here:

[LabVIEW]\resource\dialog\picktime.vi

It doesn't appear to be password-protected, so you should be able to modify it to fit your system settings. All of its support VIs live in picktime.llb next to the VI.

Do you want to use it? Would NI let you use it?

Most VIs I write ship as the source code of NI product features. It's my understanding that including open-source VIs in those features would not be allowed.

I will be at the Austin summit. I do not currently use OpenG.

Thanks, JG. I just confirmed that this bug was present in LabVIEW 7.1, and fixed in LabVIEW 8.0.

Can y'all point me to a post somewhere describing the race condition with the Copy from Folder to Folder VI? I own the libraryn VIs, so I wanted to investigate to see if something is CAR-worthy.

Looks good to me...before looking at your VI, I envisioned solving the issue just like you did...only format the visible cells. Seems like a simple enough approach that you could add a horizontal scrollbar as well with minimal effort.

How about this?

Very nice...I always use the VariantDataType VIs, and have never thought about using Flatten to XML to get more info out of a refnum than what those VIs provide. Your approach looks solid...find the <Name> tag under the <ActiveXType> tag and you should be good:

<LvVariant>

<Name>Variant</Name>

<Refnum>

<Name>ActiveX Container</Name>

<RefKind>ActiveX</RefKind>

<ActiveXType>

<GUID>{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}</GUID>

<Name>Acrobat.CAcroApp</Name>

</ActiveXType>

<Val>0x00000000</Val>

</Refnum>

</LvVariant>[/CODE]

It's not often these days that I get to add something new to my LabVIEW bag of tricks...

Sorry, I didn't mean to offend. I have deep respect for fellow yak-shavers. Maybe some day we can exchange yak-shaving tips, goodness knows I've got a few.

As for your scripting question...unfortunately, there is no way to programmatically change the image in a decoration. You have two options that I can think of:

1. If the new image is on the clipboard, you can use the "Paste" method of the TopLevelDiagram class and paste it in the same location as the existing decoration, then delete the old one.

2. If the new image is in a file on disk, then you read it in, and set the value of a picture constant on the diagram instead of a regular decoration.

Yes, I can help, I have a lot of experience with yak shaving. This video should give you all the information you need. Please follow its instructions carefully, as an unshaven yak is something to be taken very seriously.

I hate large icons. Aristos Queue loves them. If I had my way, they would have been gone long ago. Unfortunately, AQ always argues to keep them around. But since he's so badass in just about everything else he does around here, I'll pick my battles elsewhere.

This post made me realize you program without dots wire junctions... you're crazy, man.

Crazy like a fox!

Here's a weekly nugget where we described this very issue...I don't think there's a way to solve this without a "resume scrolling' button/action of some sort:

Darren's Weekly Nugget 06/28/2010

As a result of the great "Config VI Refactoring Debacle", I come down strongly on DISCOURAGING any use of VIs that are not in the palettes unless you copy them to a new location on disk and use them from there. I'm pushing to have the Variant Data Type library added to the palettes in LV 2012 so that it is no longer under this interdict.

And as most people know (based on the content of many of my weekly nuggets, as well as my penultimate response on AQ's thread linked above), I often *encourage* people to use VIs that are not in the palettes/Quick Drop. I would venture to say that, since the config VI debacle (which occurred with the LabVIEW 2009 release), we haven't had any major upgrade problems associated with changed interfaces to VIs...our developers are more well-informed of the issues, and we have processes in place that analyze our shipping VIs for interface changes between versions.

Seeing this mention of the Binary Search Pt-by-pt VI, which I would never have found, I was wondering if anyone has a list of all the vi.lib VIs that are not contained on any of the default menus? Even better, menus that expose them? Or add them to Quick Drop?

Jarrod wrote a great Quick Drop Keyboard Shortcut that allows you to easily add a selection of code (which could just be a single VI) to the user palettes so it's accessible with Quick Drop. You can get it here.