10-22-2012 08:03 AM
I have a Boolean button that is typedef. I'm doing a DOWHILE and checking that this boolean and an error cluster. If boolean OR status is true I stop the dowhile. The boolean button is showing a red dot...( coerce). I can't find anything on coercing a boolean. Do I need to worry that the boolean won't be coerced correctly? If I do need to worry how do you coerce a boolean?
Solved! Go to Solution.
10-22-2012 08:15 AM
@clint100 wrote:
I have a Boolean button that is typedef. I'm doing a DOWHILE and checking that this boolean and an error cluster. If boolean OR status is true I stop the dowhile. The boolean button is showing a red dot...( coerce). I can't find anything on coercing a boolean. Do I need to worry that the boolean won't be coerced correctly? If I do need to worry how do you coerce a boolean?
Is it a strict type def? I ran into this when putting a regular boolean into a strict type def boolean indicator (a custom display). Never had a problem.
10-22-2012 08:35 AM
Taking over someone elses code. Don't think its strict...just typedef.
10-22-2012 09:05 AM
It is..just a typedef.
10-22-2012 09:10 AM
@clint100 wrote:
It is..just a typedef.
Post an igae for use to "look over your shoulder" but I suspect LV is just reminding you about the type def... no action reqired on your part.
Ben
10-22-2012 09:45 AM
@Ben wrote:
@clint100 wrote:
It is..just a typedef.
Post an igae for use to "look over your shoulder" but I suspect LV is just reminding you about the type def... no action reqired on your part.
Ben
Post an image for us so we can "look over your shoulder." But, I suspect LV is just reminding you about the type def... no action reqired on your part.
-Google translate from beneese to english.
10-22-2012 10:02 AM
...Post an image for us so we can "look over your shoulder." But, I suspect LV is just reminding you about the type def... no action reqired on your part.
-Google translate from beneese to english.
After trying to find "beneese" in Google translate I came back to stare at this post. About five minutes latter I got it. Thanks for the auto-translate.
Ben
10-22-2012 11:50 AM
10-22-2012 12:38 PM
My question is why is a single boolean a type def? That's just another useless layer. If you are looking for a front panel sort of thing, a normal control would do the job.
10-22-2012 12:50 PM
@crossrulz wrote:
My question is why is a single boolean a type def? That's just another useless layer. If you are looking for a front panel sort of thing, a normal control would do the job.
I can think of one reason which you can feel to free to stomp on.
As a place holder for a strict type def.
Huh?
YOu can use a strict type def to force a GUI update but not with a normal type def. So the hack goes like this;
Edit the type def on the boolean
Change its look
change it from type def to strict type def
Apply changes (since they now strict the apperence is applied to all instance)
change back to normal type def.
Save all after saving the type def.
SO you get the appearence change only when you want to apply it everywhere and you are not restricted to the rules of a strict type def.
Does any of that need translated?
Ben