ShaunR

You can combine UI elements into a typedef. But you cannot have some as controls, whilst others are indicators within the cluster (the cluster is either one OR the other).

So obscure you had to look it up "TWICE"

7zip isn't a compression method. It's really a unifying (and extendible) interface to several methods the default being LZMA. As such, it's really pants to try and wrap it in LV (ever wonder why no-one has written a LV wrapper?) It'd be much easier to compile the separate dlls (zip,LZMA et al) and use those. But the OP only wants one....any one!, As long a it can do >2GB. If the openG implementation can do it then all he needs is the x64 dll and it'll plop straight in.

Name: Fast Trim Submitter: ShaunR Submitted: 03 Jan 2011 File Updated: 16 Jan 2011 Category: *Uncertified* LabVIEW Version: 2009 License Type: BSD (Most common) Just an alternative to the in-built "Trim whitespace.vi" function but much faster (3x?). It's not a direct replacement (although it could be) since it does not allow left and right trim separately. But it does allow trimming of all non-printable characters as well as whitespace if required (default is just whitepace). It's an offshoot from one of my projects that I thought may be of interest to the speed freaks out there. Click here to download this file

I'm not aware of 64 bit support for the OpenG Zip package. (I'm also not aware of a rar implementation at all). There was a discussion here a while back. Might be worth nudging Rolf nicely to see how far he got.

The NI site discusses some work-arounds. Bit it 'aint pretty. I don't know if the OpenG zip implementation is also restricted or not (2GB is a limitation of the original Zip spec, I think). But you could give that a try.

Version 1.3.0 has just been released. It is now hosted on a different server. You can download it at LabVIEW-Tools but I will still support it here as well, since I spend my life here

I would use 2 queues since command-response are instrinsicly ordered. Place your command onto a queue. When a response is received, read an element from the command queue and add it, AND the response onto another (log) queue. Then all you need to do is read the log queue to display the message-response list.

I'm not sure I ant to know what appendages you've embraced. ... Noodly or otherwise Although I'm willing to be converted if the "Halloween Missionaries" want to save me

Ooooh. Yes! and that reminds me of "PERVERT" "REVERT". For those "dead end" moments when you've been owned by the spaghetti

Rolf did some raw socket stuff a while ago that should be worth looking at.

Learn to be a plumber. They earn more than us.

The "number of rows/columns" property nodes will enable you to display different numbers of rows and cols.

Array of clusters it is then

What about 2 arrays One with the headers (channel names) and one with your data. Then you can set the fonts different for each array. < some time later after copious amount of caffeine > try this

IC (I think ) If you don't mind being platform dependent then you can use the windows SetCurrentDirectory function (LV example here). But your scripting thingy would still have to be running after they decided to save it. Other than that, I only think if saving a dummy VI after they have saved theirs (again your thingy needs to be running to monitor the memory list). But if your going the platform specific route I would suggest adding it to the places bar so they can always find it easily.

The Dialog Express VI has a start path.

No. But you do need "Windows". Here is a .NET example of what I mean.

Glad I could help

Not giving me much to go on here. What gives you the message? Is it windows/linux? It can't be in the error cluster because there is no "Memory Full" error code. If it is in the error cluster, what number (code) is it? Are you trying to dump the whole 100MB contents into an array? (What is the SQL statement?) How much memory do you have and when you get the error, how much is LabVIEW using (you can see it in task manager)?

The main difference between the NI algorithm and most others is that it removes outliers. It calculates a "best fit" using the mean squared difference method and applies a score. If iterations is set to 0, it is finished and returns the line (as in your first image). If iterations are greater than "0" it removes an outlier and then re-calculates the MSD and re-calculates the score to see if the there is an improvement. It keeps iterating until it either reaches a certain score or until it reaches the iteration number So in your second case, if you set the iterations to >0, the final point will be eliminated and it will decide that the first two are the "best fit". You need to have more data points to use this function effectively - the more, the better.

Have you tried the Drag/Drop Events?

Making Measuremnet On An Image from the Vision Concepts Manual described it in detail. The images are broken on my browser. But it describes the NI method.