Salut.
I don't remember who posted something that looked like this, but somebody talked about putting all the constant in a cluster constant(favorably a TypeDef) plugged to an indicator of the same typedef, in a vi, and then accessing them with the unbundle. So you end up with only one file containing all your constant and an easy way of accessing/adding them. Your also not limited by connector pane connections.
Can someone point me what are the problems with that solution?
I can think of two things off the top of my head: diagram real estate consumed by the unbundle and the fact that the constant is no longer treated purely as a constant... the is some code associated with accessing the constant, albeit a tiny amount of code. However, I think this still may be the all around best solution because all of the constants are in a single file and the unbundle by name would make it very clear which constant was being used... and as you mention, this would easily support constants of any type... the icon could be drawn so that it was the same height as the unbundle by name to result in pretty clean appearance on the diagram. And I'm not even sure that a type def is necessary, as there should only ever be at most two instances of the cluster... the indicator and the constant. Of course, if you used make current values default, you would only need one instances of the cluster, the indicator.
Does anyone know if there is a functional difference between using make current values default and leaving the indicator unwired versus wiring a constant of the indicator and putting the values in the contant?
George Gatling Applied Technology Division, SFA Inc. Space Physics Simulation Chamber US Naval Research Laboratory 202-404-5405 (phone) 202-767-3553 (fax)
As you know, these are open forums, you're able to come and listen to what I have to say.
-- George W. Bush, press conference, October 28, 2003
