LabVIEW Class VI Alignment Grid Size

[StevenHowell_XOM]

I use LabVIEW OOP quite frequently and I like to have a small alignment grid on my FP and BD. With LabVIEW, you can set these in the LabVIEW options for when new VIs are created, except for when you use LabVIEW Classes and VIs are generated by scripting. 

It would be terrific if there were a way to extend this functionality to OOP Class generated VIs. Currently, I have to go to the properties tab of each VI and change this manually. 

 Current settings when VI generated by LV Scripting in class. Have to change manually.

Would like an option to be able to set the Class generated VIs similar to the LabVIEW environment settings in "Options"

 This is my preference, but it may vary, it would be great to have this setting to automatically generate new VIs with desired settings, instead of doing it manually in classes. 

Thanks! 

[Mr._Jim]

Disclaimer:

I am in no way at all recommending you do this, and to do so would be at your own risk.

The following is for educational purposes only, since modifying the resource VIs can have serious consequences.

That being said...  If you were to implement your idea on your own, a file you might be interested in is:

[Program Files]\National Instruments\LabVIEW [Version]\resource\Framework\Providers\LVClassLibrary\CLSUIP_MemberTemplate.vit

I may or may not have my own style preferences regarding my class member VIs since I am a style nitpicker and coding standard zealot.  

[StevenHowell_XOM]

Mr._Jim

Thank you SO much for the er um "advice" I took a look at the VI you mentioned and may or may not have "restyled" my preferences as well.

Have a blessed day.

[AristosQueue (NI)]

StevenHowell:

You may want to edit these four VIs. They are specifically not password protected and open to edits by users. These four allow you to apply scripting code of your choice to the various tools in LabVIEW AFTER the built-in code has finished running.

resource\Framework\Providers\LVClassLibrary\NewAccessors\BaseAccessorScripter\Custom User Scripting For New Simple Accessor VI.vi

resource\Framework\Providers\LVClassLibrary\NewAccessors\OverrideRetooler\Custom User Scripting For New Override VI.vi

resource\Framework\Providers\LVClassLibrary\NewAccessors\MultiDimArrElemScripter\Custom User Scripting For New MultiDim Array Element Accessor VI.vi

resource\Framework\Providers\LVClassLibrary\NewAccessors\ArrayElementScripter\Custom User Scripting For New Array Element Accessor VI.vi

[Mr._Jim]

Thanks AQ!  I knew about a couple of those, but not all of them.

Steven H., glad to help if I can, and you have a blessed day, too.  I was being careful in my wording for comic effect, but also because I wasn't sure if mild hacking of resource VIs constitutes a licensing violation somehow.  I suppose the more proper way to do what you're asking for would be to script it.

What I did in my own case was modify the positioning of the case structure in the template and remove the free label comment (I got tired of removing it over and over again).  Then I have some scripting that runs in a couple of the VIs AQ listed above that cleans up terminal positions, etc.  (Yeah, things like terminal and front panel object control positions bother me.  I am truly a nitpicker.  )

The other thing that I did which I may request on here at some point was change the default naming convention of my accessors.  I loathe the ambiguous naming like "Write temperature.vi", since write could mean writing a setpoint to hardware, etc.  I put an "accessor_" prefix in front of all of my accessors rather than putting them in a subdirectory on disk. I absolutely love LVOOP and am fully immersed in it, but sometimes the default settings and conventions drive me nuts, especially when cranking out dozens upon dozens of accessors and member VIs on some days.

[StevenHowell_XOM]

Thanks AQ for your information as well! I appreciate it, both of you!

[StevenHowell_XOM]

Jim, I am the same way, I am a nitpicker as well, my code has to be spotless and to my liking.

[AristosQueue (NI)]

> I wasn't sure if mild hacking of resource VIs constitutes a licensing violation somehow.

IANAL, but I do not believe this is a violation for anything in the core LabVIEW. We have people make modifications to shipping VIs all the time. The toolkits are a different issue since you purchase those separately, but *everyone* already has all the core LV VIs so it does no harm to NI IP to share them further with mods. If you're worried about sharing them further, use the ni.com forums to share them.

[Mr._Jim]

Thanks again, AQ.  Knowing that, it sounds like I don't need to be so cautious henceforth, though "IANAL," myself.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.