07-26-2018 12:25 PM
@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
08-03-2018 11:48 AM - edited 08-03-2018 12:05 PM
@ahmedkochbati92 wrote:
thanks for the response ,this is the subVI
This is pretty useless for us without the caller containing all the references.
08-06-2018 04:34 AM
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.