eaolson

I like using producer/consumer type patterns. For example, one loop watches for user input, then sends a command to a waiting loop to actually process that input. Often, it's necessary for a sub VI to use one of the queues, and I'm just wondering if there is a preferred method of passing the queue to the sub VI. Usually, I pass the queue refum itself (generated by Obtain Queue) as an input to the sub VI. That way, the queue is created only once, in the top-level VI, and released there as well. Any loop in a sub VI waiting on the queue would then quit. I think I remember reading somewhere that this may not be the most desiriable way for the sub VI to get the queue. Each sub VI could obtain its own copy of the queue if it knows its name, instead. The refnums generated this way are different, I believe, even though they actually point to the same queue. Is one of these two methods generally preferred over the other? I'm still using 7.1.1, and there is a bug when obtaining multiple copies of the same queue by name, but I believe that only rears its ugly head when getting many thousands of copies, as in a loop. This would apply equally well to notifiers, I assume.

Why not just use TCP Listen as opposed to Create/Wait? It seems to largely do the same thing, but you can close the TCP connection ID it returns and recreate it later with no problems.

I'm pretty sure it's by-value, at least according to the white paper. If the wire forks and goes into two different sub-VIs, you've now got two copies of the original object. Wouldn't that violate the whole point of data encapsulation? At that point, you might as well just use a cluster.

I didn't realize you could do that. It doesn't work for me in 7.1.1 for the full string, but does in 8.0.1.

You might want to look into the Scan From String function rather than making all those string subsets and formatting them into numbers manually. It would also make your diagram a lot simpler. For the "26072006 142451.376" string above, a format string of "%2d%2d%4d %2d%2d%2d%.3f" would parse it into the appropriate numbers from which you could then build a date/time cluster.

I bet sunglasses would be a real problem, too.

Thanks. For ages, I've been trying to figure out how people made those. I tried every combination of label and frame and color I could think of and could never get it to work. Never realized the dialog label was different from the decorator label.

I realize that this is a new reply to an old thread, but I'm just starting to work with OpenGOOP and found this behavior to be annoying as well. But in trying to use the solution that mballa suggested, I can't seem to get a "Make Strict Reference" method from the VIRef invoke node. I've checked in 7.0, 7.1, 8.0, and even 5 (don't seem to have 6 anywhere around here), and it doesn't seem to be present in any of them. Was this specific to version 6, or am I looking in the wrong place?