Default VI file name

[Bjarne Joergensen]

HI

When saving a new VI LabVIEW default name it "Untitled#x.vi".

Is is possible to change that to something else like "TSVWS - #x.vi"

An maybe also popup a warning if you try to rename i without "TSVWS - " as prefix.

 

regards Bjarne

[crossrulz]

Not that I am aware of.  But yourscheme is not much better.  You really should have descriptive names for your VIs.

[Bjarne Joergensen]

Please don't misunderstand me ?

My intention was to remind my developer group to remember the prefix on the file names and make them sure they don't want the prefix if they try to save without! 

[PiDi]

There is no direct method.

BUT we can always hack something. I've attached a little plugin that allows you to change the default name of the newly created VI. It's based on project providers magic, so use this at your own risk (this is the dark magic we're talking about here  ).

Instructions:
1. Install this package.
2. Go to <LabVIEW>\resource\Framework\Providers\DefaultNamesChanger folder
3. Open DefaultNamesChanger.ini file.
4. Edit "VINameTemplate" key.
5. Save the ini file and restart LabVIEW.
 

pidi_lib_defaultnameschanger-1.0.0.6.vip

[Aristos Queue]

I think you could do this by modifying 

<LabVIEW>\resource\plugins\lv_new.vi

I'm telling you how to cut into LabVIEW's internal operations. If you break that VI, you could lose functionality you care about. Make a backup copy first. 

[Antoine Chalons]

AQ, this VI seems to be password protected, at least in LV 2014 and 2016.

[Neil Pate]

And 2015

[DTaylor]

10 hours ago, Antoine Chalons said:

AQ, this VI seems to be password protected, at least in LV 2014 and 2016.

 

9 hours ago, Neil Pate said:

And 2015

Using this is almost assuredly a violation of license agreements:

http://www.hmilch.net/h/labview

[Aristos Queue]

Hm.... well... that's frustrating. I've tried to get as many VIs as possible out from under password lock. I thought that one was clear.

I'd suggest you just save over it, but it looks like it handles quite a bit. I'm guessing this one is still password protected because there's some bits in there that could be easily unstable if used under different conditions.

Sorry to get your hopes up.

[Darren]

Another option is creating a lv_new_vi.vi in that same folder. This VI will override the behavior of pressing Ctrl-N. You can find the required conpane for the VI on labview wiki somewhere, but I think it's just 4x2x2x4 with an I32 in the upper right. Unfortunately (due to its age as a feature) it has no knowledge of application instances, and thus doesn't work properly when pressing Ctrl-N under different containers in the project window.