Cat

No answers, just that I feel your pain. I too had code with a memory leak and talked my boss into letting me buy Desktop Execution Trace Toolkit. It didn't help any. I think if you have a really small project it might be useful, but there was just too much going on in mine and the trace buffer quickly filled up. Too quickly for it to be of any help (my memory leak wasn't evident until a few hours of run time). Hopefully your boss will be more forgiving.

A looong time ago (2001?) when I was designing a GUI I needed to be able to show from 1 to 4 waveform charts on 1 screen, in separate plots. If there was 1 plot, there was 1 big chart, if there were 2 plots, there were 2 narrow horizontal charts, and if there were 3 or 4 plots, they were each in 1 quadrant of the screen. To make it even more fun there are two different sets of plots (the other is an XY graph) I need to do this for. At that time my intention was to stack all those plots on top of each other and make them visible/invisible as needed. This had a tendency to crash my computer. There was some issue with LV back then about stacking lots of stuff on top of each other and manipulating it in that way. So what I did was instead of making an unneeded plot invisible, I moved it to another (hidden) part of the FP. When I needed it again, I moved it back to the right place and resized it according to how many plots there were. While painful, this has worked okay. Flash forward to 2010... my Users now want to be able to resize their windows on-the-fly. While LV does allow one to "Scale Object with Pane" for selected objects, it unfortunately gets very confused when those objects are off on some other part of the FP. Not that I am surprised or would expect otherwise. Since my current layout doesn't work, I've been revisiting the stack-and-hide concept. This seems to work better with the resizing, as long as you don't get too wild with it. My question for you all is -- have any of you tried this with recent versions of LV? I will have somewhere in the neighborhood of 19 plots stacked on top of each other. This is going to take some major recoding, so before I head down this way I thought I'd check around here and see if anyone had any experiences with doing this. Cat

I'll second this. We installed these in a bunch of boxes several years ago and have had no problems. I've been wracking my (fuzzy) brains trying to remember what brand they are. I can't tell from just looking at them since we've stripped the boxes off and just use them as bare boards.

Yeah, sorry about that. I really have to stop sneezing all over my keyboard.

Sounds like the direct result of Global Warming to me! (is there a "duck and cover" emoticon somewhere? )

Stop! You guyze are killing me! I have to stop laughing so much because that just starts yet another coughing fit! (and NO comments about bringing up fur balls, please!!)

Aww....! Oh, geez, you should have issued a non-sequitur warning with that post. Now you're making me think about comfort food. I'm having visions of swimming around in a bowl of macaroni and cheese. Yup, I'm on good drugs!

I really didn't want to hear it's going to be weeks... About 4 days into it (last sunday) I had to drive some equipment to a test site for installation - 4 hours away. I had people lined up to call me every half an hour to make sure I was still alive and hadn't passed out and driven off the road.

LOL! I'm glad your cold class thread self-terminated. Unfortunately, I discovered the Cat.SinusInfection and Cat.Bronchitis properties were set to true, also. I am applying the TakeAntibiotics method, but am now also suffering from the Cure.WorseThanTheDisease property.

...it would be able to cure the common cold. I could use that right now. Maybe there's something in all that OO stuff I don't know about yet. A "cold" parent class with a "common" child and a "cure" method? I'll check into it when my brain's a little less fuzzy...

You're not missing anything.

I am REALLY tempted to abuse my temporary moderator privileges and kill this thread. Of course then I'd probably be accused of being a member of Mossad or a prostitute or an animal or a thief or a cannibal or just plain stupid. There were a few interesting things talked about here a long time back. But not anymore (despite attempts from posters other than alfa). This will be the first thread I've ever felt like I had to stop watching, but it's my little form of protest over letting one person continue his political ranting on this forum. BTW, just for the record, some of my best friends are animals.

But after a lot of costly bug fixes, Darth = Good.

Version changes concern me. They mean a lot of work for me revalidating my 1800+ vis. That's the main reason I went from 7.1.1 to 8.6.1 and bypassed all the other versions. I figured by the time 8.6.1 came out, all the bugs were out of the version 8 software. So NI's new "Major Version Release Every Year" paradigm really concerns me. When they release software with a new major number that means to me they have made major revisions/additions/changes. Otherwise, why make it look like a different product? I don't need a lot of fancy new features every single year; I need to know the code I already have is going to work and not be broken when I upgrade. Even worse, I don't want something to still work, but work *differently* from the way it did before (this one bit me in 8.6.1 -- so much for waiting). I would much rather see LV2009 SP2 be released next August, not LV2010. And if LV2010 will be, in essence, just more bug fixes for LV2009, then NI shouldn't change the version number. I would actually feel comfortable upgrading then.

Cat = seeker169 http://forums.ni.com/ni/profile?user.id=119564

But even if there's only one property node, every time the value out of it branches, isn't there a possibility (probability?) that a data copy is being made anyway, depending on how the value is being used? Either way, AQ's last point about readability is an important one. With code this bad, a good intermediary step can be to put the property nodes right by where they are used so that you can get a better sense of program flow. Then, once you have it all cleaned up, take a step back and see if you can consolidate all those property nodes in a logical way. It is stylistically "better", and a good habit to get in to, since it's an absolute necessity if writing code where a particular value might be changed in between property node reads by some other part of the code.

Yeah, I thought about that a second after hitting the "reply" button. But whenever I attempt to edit a post it either ends up looking all garbled or just blows up (IE6). Tim_S had already beaten me to it anyway.

Oh and I feel your pain. BTDT... BTW, if you don't already know, you can right-click on a subvi and select Visible->Terminals to really see where the wires are going.

Double-click on the wire and the entire thing will be highlighted.

Only someone who is vewy wude.

Wow! Lot's of pretty colors (yes, after being pretty much house-bound for 4 days, it doesn't take much to amuse me )! Gary, here's a local site that's been doing a great job of predicting totals. They were even spot on with the December storm and predicted the large snowfall long before the NWS/TWC had a clue it was going to be as bad as it was. http://www.footsforecast.org/

I think the weight of all that snow on top of your internet cable is slowing those 0's and 1's down.

The only silver lining in all of this is that my power has stayed on [knock on wood]. I have a gas fireplace that can put out some heat, but no where near enough to cope with the low temps we've been having. Honestly, if it wasn't for the fear of power loss, by this point I'd just throw my hands up and say, "Bring it on! What's another 20 inches?!" Oh and then there's the fear of my roof caving in...

Can you say... 10-20 more inches tomorrow?? I can't. I'm in severe denial.

I'm *really* glad you clarified that! Michigan is my very favoritest State -- in the summer. Winter's starting to look good too, now...