LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

show hidden controls and indicators


@billko wrote:

@Ben

... 

Please note that when a VI hits a breakpoint the "Font Dialog Dropdown" turns into a call chain indicator that you can use to figure where the VI is being called from in the application.

 

Ben


Really!!?  I never knew that!!!  Thanks for the insight.  🙂


You are welcome.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 13
(532 Views)

@ahmedkochbati92 wrote:

thanks for the response ,this is the subVI 


This is pretty useless for us without the caller containing all the references.

 

  • What is the purpose and expected result of the string comparison? Is this string numeric? Note that string comparisons use alphabetical order, not numerical ("1234567" is smaller than "7", for example!)
  • What are typical values for all the string controls (e.g. "target")
  • Are all the autoindexing arrays of references the same size? If one is smaller or length zero, it will force the number of iterations to be smaller.
  • Why is there so much unnecessary duplicate code? (For example, your inner case contains identical code in both cases, the difference is a single boolean that you already have! see picture!)

CodeDuplication.png

0 Kudos
Message 12 of 13
(511 Views)

This might be used to show hide copied buttons on different tab pages. Makes me think there should only be one of each buttons, laying over the tab control. Then the showing hiding makes sense. If each page has copies of the buttons, why not simply delete the ones that should not be visible? If you use a tab control at all, it could also be an attempt to make some manual tab page surrogate?

 

And this will cost you points at a CLD, but I'd probably not wire those property node error outs. The only way it's going to give an error is if the refs are incorrect, something that will only happen during development, I assume.

 

Or I'd put those refs in an array and set all visible properties in a for loop. That would make me think the input arrays of references might actually be a (transposed) 2D array...

 

Hard to say how to improve without some rational\context, but I don't think this would be my final version.

0 Kudos
Message 13 of 13
(487 Views)