LabVIEW Idea Exchange

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

Class property accessor VIs should be scripted to the actual LabVIEW settings

Status: New

I find myself to replace controls to the preferred style and reorganize the labels (trough the quick drop shortcuts) for almost every accessor VI. For this purpose I ended up modifying the templates of these VIs, but I would prefer to have this in the script that creates these VIs, so they automatically match the setting made in LabVIEW options. This should include preferred control style, label placement of the controls on block diagram and also the front panel cleanup.

2 Comments
BertMcMahan
Trusted Enthusiast

There's a VI you can edit to add custom scripting to any Override scripting you do. See my reply to this thread:

 

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Front-Panel-Terminal-as-Icon-Should-Respect-User-s-Op...

fefepeto_kb
Member

@BertMcMahan, I do know about that VI, but I would like to skip a one or two day of work to just cover all the use cases, since the style is not a 1:1 match to the defaultControlStyle key in the INI. There the values range from 0-4 and then there would be massive case structures to just translate these values to the Style ID. The Style ID is the input that's required both for New VI Object and Replace method, available trough invoke node.

I think for just one style, modifying the template and setting the default style is a more effective workaround.

Creating the script on the other hand shall cover all the use cases in my opinion.