asbo

The suggestion is still in the right ballpark - after the Find dialog selects the hidden label, you can scroll around and find whichever constant is also selected. Right-click > Visible Items > Label. Then you can clean up the label as necessary.

If I remember correctly, someone used it to read the names of case structure cases a while back. I'll see if I can find the thread I'm thinking of. It was actually an event structure. Here's the thread. Apparently it implements its own OCR, my mistake.

This article on getting and setting IMAQdx attributes may get you going in the right direction.

That's correct, our VIPM packages install to LabVIEW's user.lib folder (though the package software supports just about any destination you can dream up) and when we write our applications we just drop those VIs from the palette. We maintain a separate repository for the "source" versions of these VIs where they can be developed and repackaged into a .VIP file. Just like VIs that ship with LabVIEW, it's considered a faux pas to edit any of these reuse VIs that were installed via package. It does take a little bit of setup, but when you've got it streamlined it's a brilliant system. We keep a .VIPC (VI Package Configuration) file in the project's folder which is more or less a list enumerating which packages the project uses and which version of each particular package is needed. Coupled with a network drive that houses all of our released packages, it's extremely straightforward to install all the necessary reuse for a project on any machine.

Aww man, I hadn't noticed that ... What has been seen... Being Android, I'd be surprised if someone hadn't written an app that spoofs User Agent, but maybe not ...

You won't know until you try. Trying 32-bit calls on 64-bit certainly won't set anything on fire, but it looks like there is indeed a 64-bit version of user32.dll that will be seamlessly called if you don't use an absolute path.

The NULL character isn't white space, much less a printable character, which is why neither of those VIs did (or should) remove it. Search and Replace is a good way to do it, or if you know your data will always have 4 NULL characters prepended, you could use String Subset, which may garner a performance gain.

When you have dependency conflicts in a project, the "Project Dependency Conflicts Detected" dialog pops up and has Close and Help buttons. The Close button should really be an OK button, the first time I encountered it, I thought that LV was either going to close the project or not load my VI.

Thanks!

One thing I've noticed already is that previously when opening links from the View Unread Content page, it would jump me to the latest unread post. This no longer happens. I dig the new theme, though.

I hope that didn't come across as cutting, I was just pointing out another way to look at it. This is perhaps side-stepping the problem, but we use VIPM packages for all of our reuse code, which installs to vi.lib and doesn't get versioned with project code. Instead, we version a VIPC file which lists all the reuse code the project needs and what versions of the reuse package. This might be a useful workflow change for you to consider. If you'd like to solve the problem in SVN exclusive, I'm afraid I don't use tagging in depth enough to be more helpful. Can you simply not select the utility folder when doing the tag, or are the utility VIs versioned per applicaion? Maybe a folder structure diagram could help clarify?

What if your utility VIs change? Every time you update reuse VIs, you run the risk of breaking code that calls it. Seems to me like it would be a good audit of how your reuse VIs are being used as well, so long as your tags are along the lines of "applicationname-beta-n" instead of just "beta-b".

I've only done it before with calls relating to shutdown/standby/hibernation, but you should be able to acquire a security token for your application which grants you elevated privileges. I did not deal with UAC, but I know that UAC is compatible with the token system. Poke around on MSDN for some details. It's common to use application manifest files to require these privileges but you can do it programmatically with the Windows API as well. I may be writing a wrapper for the WLAN API soon, so this might be helpful to me as well. If I find some spare time, I'll have a look as well.

It doesn't just support integers, each cell is actually a string. You use property nodes to get/set these values. It's a very powerful control if used properly, go to Help > Find Examples... and search for listboxes. Check out the Properties Tutorial example.

It's a Multicolumn Listbox. If you right-click the control on the front panel and go to properties, that dialog will have the control type in the title bar. Alternatively, right-click the control on the block diagram, select Create, then Reference and the reference you drop will also have the name of the control type visible. The integer value you can read/write is the 0-based index of the row which is selected.

FWIW, the WM_CLOSE method works fine on a copy of the OSK I launched from the start menu. I do have UAC disabled, however.

OP probably just wants some background reading, instead of just an answer.

Tough to diagnose without a block diagram. Can you post it?

My brain died a little here.

Crap, why does this have to be an hour long? I do want to watch it, though...

Ding ding ding! It's all good-spirited though.

Posting a screenshot of your block diagram would be much more useful. Likely you're telling VISA to use a port that doesn't exist.

That's a relief, I thought there was something wrong with me. I get plenty of flak for using it so much (feel free to chime, hooovahh).

That's awesome! Truly one of my favorite features in LabVIEW, it makes me so much faster. Like most, I came from text-based roots and I'm much, much better at typing than mousing around, which has the perk of not having to learn which function is in which palette.

Interesting suggestion. Just out of curiosity, what makes you think it would be GDI-related? I would think that LV shouldn't need any rendering resources during a build. This could be checked by adding the GDI Objects column to Task Manager, though.