LabVIEW Idea Exchange
I've encountered quite a few limitations when debugging debuggable PPLs, and feel that a number of improvements could be made to this process. I often find myself having to open a second project with the specific dev library in it, and then toggling back and forth between the two which is both confusing and inefficient. This is just scratching the surface, but here are some improvements I'd like to see made:
- Non-editing menu options should remain available. One I use quite commonly: right-click on a class cube, and select "Show Class Library". But it's not available:
The workaround I use is to "Copy Data", press ctrl+n to create a new VI, drop the class cube there, and then right-click on that and select "Show Class Library", then toggle back to the temporary VI and close it. - VI Properties aren't available in VIs:
I often want to double-check reentrancy settings on VIs to ensure everything's configured correctly. - Private class data isn't shown. I get why this isn't available in non-debuggable PPLs, and I understand that there's a healthy debate that can be had as to whether or not this should be available in debuggable PPLs. I'm of the opinion that private data should be available in debuggable PPLs as they are meant for debugging, not for distribution.
- Private class methods don't show up in the project. But if you click on the sub VI for a private method, you can open up the block diagram. If the block diagram is accessible, it really should show up in the project. I often find myself searching for a VI in the project, and not finding it anywhere, because the method is private.
- Unusual interactions. I've seen a number of scenarios where I'm prompted with requests that I shouldn't be asked. For instance, if I double-click on a malleable VI in a PPL's block diagram, I get this popup:
2 Comments
