05-06-2008 08:22 PM
Thanks smercurio
http://forums.ni.com/ni/board/message?board.id=170&view=by_date_descending&message.id=321546#M321546
LOL!! 😄
05-07-2008 04:01 AM
In more places "abuse" or "over-use", in one or the other way.
@smercurio_fc wrote:
That's a bit excessive, in my opinion. Every programming construct has its use. It's their misuse due to inexperience that's the problem.
@JoeLabView wrote:
It is a formal requirement within my company that forbids the use of Local Variables and Stacked Sequence Structures.
05-07-2008 04:06 AM
JoeLabView wrote:
Property node is a better way to go as you can also use it to change the text value as long as you are displaying Caption text.
I think you wanted to mention the Boolean Text, not the Caption Text.
Because, Boolean Text.Text enables you to change the value of the boolean control when we simply click even on the text. ![]()
05-07-2008 08:14 AM
05-07-2008 10:42 PM
Thats what intrigues me, Joe.
When the Label name should(must) not be changed anytime during the program, why was the feature to change it left to the programmer on the first hand? ![]()
IMO, NI should have disabled & greyed it out or not given at all. ![]()
05-08-2008 06:57 AM - edited 05-08-2008 06:58 AM
Well..
It is possible to modify configue another VI which is not running. Although I didn't try it, you may be able to change the label. Or if you have a VI whose purpose is to programmatically create another VI (which is not running), then you would want to change or create the label.
As you realize, you can't change a label while it is ruinning. First of all, it wouldn't make sense, and second, there are objects behind the scene that have to keep track or references to that object. So if the object name (reference, etc) would be dynamic at run-time, it would either be a headache to keep track of it, but most likely asking for trouble.. 😉
So it does have it's use..
RayR