DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
doyles

API Tester automatically sets Block Diagram buttons visibility based on RTE

Status: New

Accepted. We think it's fair to do something here. Whether it is disabling the button, a popup, a warning...

In our backlog for a future DQMH release

I saw that this request for automatically refreshing the modules was released: https://forums.ni.com/t5/DQMH-Consortium-Toolkits-Feature/Auto-press-the-refresh-button-on-cloneable....  I am thrilled that idea was submitted, approved, implemented, and released by the time I got here to submit the idea.

 

I believe there is one other aspect of the API Testers that should be configured by default: the visibility of the Show Block Diagram and Show Diagram on Init buttons.  Since these buttons have no use in an executable, they cause confusion for operators.  I would propose the following code is scripted (instead of me needing to add it to every API Tester):

 

doyles_0-1733522390211.png

doyles_1-1733522397990.png

 

Thanks,

Scott

2 Comments
Darren
Proven Zealot

The API tester is a debugging tool and (in my opinion) should not be an operator-facing VI.

mbaudot
Active Participant
Status changed to: New

Accepted. We think it's fair to do something here. Whether it is disabling the button, a popup, a warning...

In our backlog for a future DQMH release


Matthias Baudot | Software Architect | Founder & Owner at STUDIO BODs | DQMH® Consortium Board Member & Trusted Advisor

STUDIO BODs     LabVIEW Champion     Certified Professional Instructor     DQMH Trusted Advisor     DQMH Consortium Board Member     GCentral Sponsor

 Check out my LabVIEW presentations and videos!