Improper use of prop node?

[plyons]

Hey folks, 

I dealing with some property nodes that don't seem to be functional... I was wondering if you guys have dealt with this or if there's something I'm doing wrong.

I'll attach a png of the case that executes the code in quiestion.

Probing the input to the prop nodes shows that they are receiving the "enable/disable and gray" data, but only two of them appear to be executing (actually disabling and graying the control).  "Current Altitude" is a numeric that works fine as a prop node, as does "alt up" which is a bool button.  

The others, are bool buttons and a listbox (Altitude(ft))...

Ive tried explicit and implicit... with a ref...   anyone see what im doinng wrong here?  or is there features/properties of the individual controls I should look into?

thanks for any thoughts

-pat

edit: I've noticed I've goofed up somehow and I have two usernames for the forums here- who do I talk to or contact to delete one of them?

[crossrulz]

Is there an error being thrown?  Are these properties edited somewhere else (possible race condition)?

[RavensFan]

Nothing looks wrong from a simple picture.  What makes you say they are not functional?  What are they doing wrong?  Could you have an error on the wire that is preventing later property nodes from executing?

Post a simplified VI that demonstrates the problem so that we can poke at it.

[JÞB]

---

@plyons wrote:

edit: I've noticed I've goofed up somehow and I have two usernames for the forums here- who do I talk to or contact to delete one of them?

---

Jordan (She will probably contact you via PM or E-mail to clairify )

[plyons]

@crossrulz - I have an error handler that will report any propagated errors (even probing it I see no errors)

@RavensFan- The controls do not become disabled and do not gray out, I will tyr to make a small vi to post up - maybe it will work in the small VI but not the larger UI ive built

thanks!

[RavensFan]

Don't make a VI.  Make a copy of the one you have.  Then strip out everything unrelated to the problem at hand.

[plyons]

Ok, well I've made a small VI with implicit.... or is it explicit... I can never remember those two... I made a VI that has prop nodes for each control (without the refs wired in haha) and it works fine... which means that the problem is in my much larger code...  it's an old 'framework' of spaghetti code... ugh this will not be easy...

I guess I shouldve done this before even posting- thanks for the suggestions

-pat

edit: ravesfan- I missed you last post- the code it's in is super sloppy, confusing, and old (compared to the framework Im using now), there's ~5 state machines in one vi.  To quote a reddit user's description of some LV code, it looks like a unicorn threw up colored spaghetti haha...

[crossrulz]

---

@RavensFan wrote:

Don't make a VI.  Make a copy of the one you have.  Then strip out everything unrelated to the problem at hand.

---

And after you delete something, make sure your problem is still there.  That's usually a good way to widdle down to the source of your problem.

If you aren't having an error, then you either A) have a race condition or B) have multiple controls with the same name and you are looking at the wrong controls.

[altenbach]

(Maybe you accidentally used an "improperty node" instead?) 😄

Waiting to see some code .....

[plyons]

haha yea, if an improperty node are two canceling nodes back to back - Sry to dissapoint, the issue I had was far more typical than I thought-  turned out to be a race condition...  There were so many property nodes for some of these controls I had missed a few that were being executed almost right after the 'disable' nodes were executed- Had I run it in highlight exec. mode I'm sure I would have caught it earlier...  n00b mistake, thanks for the help though! and kudos to you guys.

-pat