When I need to edit a VI I didn't write, I find it irritating when the VI was created with IDE preferences that don't match my own. So I wrote this plugin that will "Nattify" any VI at the press of a button (Ctrl-Space, Ctrl-N to be specific). Nattification currently does the following:
If you don't want to modify the panel appearance, you can type 'p' in the Quick Drop window before pressing Ctrl-N. This will skip cleaning up the panel and changing its color.
I understand you may not share all my same preferences. But that's cool, the code should be very easy to navigate (since I implemented it as a Natt Sequence), so feel free to install the plugin, then add/remove/modify any of the existing functionality to match your preferences. If you do add anything, let me know in the comments below, maybe it's something I'd also like, and I just haven't thought of it yet.
This plugin can be used with LabVIEW 2014 and later. Default key assignment is Ctrl-N. See here for installation instructions. Make sure you place the support LLB next to the Nattify.vi on disk.
P.S. - If this sounds familiar, I wrote a simpler version of this tool as part of my Don't Wait for LabVIEW R&D... Implement Your Own LabVIEW Features! presentation at NIWeek 2018.
This is awesome, thanks for sharing this Darren! I used this today and went a bit crazy and decided I needed to Nattify all of the VIs in a project. So I made this little VI to wrap a slightly-modified version of your Nattify.vi* and apply it to all of the VIs in a project. I thought I'd share it in case anyone else finds it useful or is trying to do the same thing.
I'm using LabVIEW 2019 so if anyone needs it in a previous version I (or someone else) can save it in a previous version and upload it.
Since this uses a version of Darren's Nattify.vi it needs the support llb next to it on disk. I found that in one of the VIs to align the front panel it uses a feedback node which makes it have a bug when calling it a few times in a row, so you will need to use this other support library instead.
*The only change is it passes out the vi ref and doesn't take in some of the inputs that are only needed for quickdrop.
Thanks for sharing your additional Nattification tooling, Dani.
FYI, I just posted a small update to the Nattify tool. Now, if you type 'p' in Quick Drop before pressing Ctrl-N, the tool will skip the panel cleanup and changing the panel color. I did this because I found myself wanting to Nattify UI VI diagrams, but not change their panel appearance.
@danijobe - Would you be able to save this for LV2018 or earlier? I havent moved to 2019 yet, and I was wanting to use your project version. Thanks!
I used a VM and loaded LV2019 to back save to 2018.
Attached are the original VIs from danijobe saved in LV 2018.
I also modified the NattifyProject VI to only Nattify the vis in the root of the project, and to exclude dependencies. I did not want to modify all the default NI code and other dependencies, only my VIs actually in the project.
For those of you using Nattify on your entire program structure, especially large programs you didn't create, consider modifying it so that if a subVI has "Show front panel when called" enabled in the properties, it doesn't rearrange the front panel. That way pretty much all of the UI subVIs will skip it automatically unless the VI uses FP.Open and FP.Close nodes.
Darren, thanks for your wonderful tool!
I added following feature: If you type anything in Quick Drop before pressing Ctrl-N, the tool will show a FP where you can choose which steps of Nattification you want to happen.
Further I splitted Arrange Windows in two steps FP and BD and I modified Icon View in order that it leaves References and Classes as icons as these icons show extra information.
The VIs are saved in LV2018
Hi everyone, I´ve added the following option: "Separate compiled code from source file" to help with your Source Code Control.
It is usually something I need to check as I'm an SCC regular user, so I think it could be another Nattify step.
Darren, thank you for this awesome tool!
The VIs are saved in LV2018
Hi, thank you for this useful tool !
I wanted to add some features and I finally made a lot of modifications to be even more practical and also for more reusability !
Here, some modifications I have made :
I am glad to share this with you.
Loïs LE BRAS