asbo

On Windows, you can use the ShellExecute API call to execute "mailto:name@address.com" and the default e-mail program will be launched. You can use the exact same API for URLs.

That's awesome. So, when will something like that be shipping with LabVIEW?

My Coffee cup: How to clear or Reset COM port ? 1188 - RESETTING YOUR COMPUTER'S COM PORT ASSIGNMENT

I don't, but if you felt like writing some scripting...

Out of curiosity, what kind of throughput do you see? How big (generally) are your payloads?

If you consider PPLs as a baby step toward a built EXE, then you can approach them with the right mindset: valuable in certain use cases, but completely useless in others.

Hmm. I would if it could be made useful in a production application? The only possibility I can come up with is if you have multiple UIs and are too lazy to defer each individually.

Yep, the built-in search is pretty much garbage. I almost exclusively google site:lavag.org whatever my heart desires.

Does Active in this context to the VI with FP focus? If there's any context help for that I don't have the ability to reference it right now.

Have you seen the Quake 3 Source Code Review articles? There's some very interesting stuff in there. He also has articles on loads of other id software. The English version of that article is not nearly as well fleshed-out.

The obvious step further with this is an event structure, but that's only necessary if you need to respond to a variety of events, user input, and so on. The notifier method is clean and simple if you only have one source of interrupt.

Easy answer: instead of calling Quit LabVIEW, use System Exec to run "taskkill /f {appname}.exe". Hard answer: break down all of the technologies (DAQ, TCP, Shared Variables, etc) you use and figure out which one isn't shutting down properly. You failed to mentioned the version of LabVIEW you're using but I'll assume it's LV2011. Try turning off SSE2 optimizations in your build.

Update the lvsound2 library (Sound Input/Sound Output VIs) to support changing audio devices on-the-fly.

There isn't a way to re-bind CLNs that I know of (there might be a scripting method, but...). If you configure the CLNs with a specific (e.g., ".\bin\sqlite.dll") that gives developers the opportunity to replace it on disk with which version they prefer. Personally, I do not see value in being able to wire in the path of a DLL to use. If you have to programmatically determine what version of a library to use... Do CLNs load their library at load-time or run-time? If it's the later (I believe it is), then you have up until the first CLN call to programmatically copy a different DLL to your relative location. In dealing with an oversight I found in the lvsound2 library recently, I was experimenting with forcing a DLL to unload unilaterally. Unfortunately, it does not seem this is possible. With that in mind, if there are a subset of specific functions (e.g. sqlite_version()) which might need to be called as part of the logic to figure out which library to use, it would be wise to wrap that in a dynamically called VI so that the DLL does not attempt to stay resident.

I have the same vague recollection. How may vague recollections make an actual recollection?

As a general warning to anyone interested, I guarantee you'll be able to crash LabVIEW with these, so you're nuts if you even think about using this stuff in production code. A few issues I know of: 1) The compiler gets confused when you stack them deeply as subVIs. Not sure why. 2) If you copy your VIs to a new machine where they've never been loaded before, your load time goes through the roof for first load, so much so that most people might believe LV is hung and kill it. 3) These VIs do not play nicely with recursion. It's a very cool toy, but like Yair mentioned the experiment is essentially over. I'd love to see a stable replacement for this kind of concept (think of the possibilities for reuse...).

Have you analyzed it at all? What frequencies are present in the noise?

If I had to guess, out of your native tongue to x while simultaneously into your native tongue from x.

There have been a couple other posts on this by ShaunR and Daklu - primary speculation is either disk corruption (by me, no shame) and antivirus/etc locking the disk.

Thanks for the replies, rolfk and Mr Mike. Had I thought it through a little more, that'd have been obvious. I'm glad to hear that the application process for nodes is thorough, at least. The VI approach, while less controlled, does make more sense in these instances.

Neither of your questions are clear, can you elaborate?

Does it have to be HyperTerminal? What about just one iteration of using VISA calls?

I can't test it right now, but what about a conditional probe in the master VI?

I'm sure I've said this before, but I am seriously jealous of your low-level knowledge, particularly of the Windows operating system. Bravo, I look forward to seeing the library. I agree that the taskbar interface is so marginally useful that I would actually be disappointed if NI wasted any time on it. There are so many things that would be better served with developer time. If you want some examples, just scroll through the top kudos'd ideas on the Idea Exchange. However, if you really do think it's that valuable, you should add it and see if you can garner support for it.

I'm in this camp. Given that the kid was keen enough to throw in protective clauses, I'm surprised he let this slide. I've gotten into arguments over less.