B Chavez

QUOTE (vultac @ Nov 29 2008, 06:43 PM) If you want to leave the lower two bits alone, then simply increment by 4; incrementing by 8 leaves the lower 3 bits alone, by 16 leaves the lower 4 alone, etc.

Would something like this work? It basically divides your long wait into many small waits, checking a control each time.

If you're running the VI multiple times without closing it between runs, the indicators will not clear unless you add code that does it before everything else, or do what Syrus suggested. QUOTE (syrus @ Oct 23 2008, 03:15 PM)

QUOTE (Val Brown @ Oct 10 2008, 07:57 PM) I'm no math wiz, but my first thought is that if you need scaling, you've gotta multiply or divide. I'd be interested if someone has another way.

I think this is what you're after. Download File:post-1591-1223692606.vi

QUOTE (Norm Kirchner @ Aug 20 2008, 11:17 AM) This isn't any cleaner than 'IP to String' but it does show how the integer represents the IP.

I've been using a IBM Lenovo laptop with a 15.4" widescreen and I'm pretty happy with it. It's a fairly large machine but most of the size is in the width and not depth. The widescreen is very convient for having multiple windows open. The only thing I wish I had was a little more resolution, I've got 1680x1050 but you can now get 1920x1200, which is perfect for two pages side by side (and can display 1080p natively). In the office I have two 17" lcds that are only 1280x1024, the minimum resolution I can stand. But I'm working on upgrading to a 24" widescreen with the 1920x1200 I mentioned above.

Take a look at this thread. There's a few examples that come close to what you're looking for.

And with regard to the second question, adding a 'timeout' event allows the loop to run again and sets the KeyFocus as expected.

Set "Update Value while Typing" on the string control and it works fine. It seems that pressing 'Enter' fires the "Ok": Value Change event but the control has not been updated, it's still being edited.

QUOTE(orko @ Aug 31 2007, 12:10 PM) My front panel activity gets locked out for some reason. It seems to happen when I click just below the slider, on the scale. I tried un-checking the "Lock front panel until the event case for this event completes" box, but it still happens. Anyone else seeing this behavior.

Take a look at <LabVIEW dir>\examples\general\strings.llb. There are a two VI's "Parse Postfix Expression" and "Parse Arithmetic Expression", one of the two should do what you want.

QUOTE(Omar Mussa @ Aug 20 2007, 11:41 AM) Even more concerning is that if you lower the millisecond delay to zero and let it run for a little bit, the Mean values 'go out of tolerance'. It looks like the point-by-point mean keeps an array of x values and a running sum. The problem is that it adds the new value to the sum and subtracts the oldest value from the sum, resulting in some rounding errors that accumulate over time. What you end up with is a sum that does not exactly equal the sum of the 4 values.

I've attached what I think it should look like in LabVIEW, it gives the same result as what PJM posted. See what you think. http://forums.lavag.org/index.php?act=attach&type=post&id=5067

What do you use to create/edit *.emf files? Thanks