Stop hidden folders appearing in Templates (ie File:New..​. dialog)

Question

Hi All,
I have a sinking feeling that I'm going to be sweet out of luck on this one, but it's worth a shot...
We currently have two versioned folders for our company's reuse library (one in user.lib and one in instr.lib) so that things nicely appear on palettes without the need for 3rd party software etc. To complement this, today I was thinking that those VIT files we have could be even better placed in the Templates folder of LabVIEW so that when we go to File->New... we would be able to see our various company templates, etc....
However, when I tried this, the hidden folders etc that Subversion leaves also appear in the templates dialog so I end up seeing something simliar to this (there is only one VI, called "Wizard Dialog.vit" in the new templates folder right now):
From Templates
|-<Company Name>
|     |-.svn
|     |     |-prop-base
|     |     |     |-Wizard Dialog.vit.svn-base
|     |     |-text-base
|     |     |     |-Wizard Dialog
|     |     |-tmp
|     |-Wizard Dialog
|-DAQ
|-Frameworks
|-etc 
Is there anyway to stop LabVIEW from showing the hidden Subversion files? (I tried turning on the setting to use _svn folders instead of .svn but got the same result)
Shaun 
Message Edited by shew82 on 06-18-2009 05:46 PM

Answer 1

Here's the background:
Some of the issues that we have had with our reusable elements in the past is
1. Ensuring that the various developers get the updates (ideally as automatic as possible)
2. Ensuring that the process for creating new reuse elements and updating existing is as streamlined as possible. In particular, an earlier process required that each template, etc be manually reviewed by a panel. Whilst this sounds good on paper, what was happening was that the review board would often get busy and things just wouldn't happen.
We therefore wanted to look at other options for allowing more creative freedom to the various engineers that could keep the reuse library alive. It was thought that a versioned location in user.lib, instr.lib and templates would allow any of the engineers (of which almost all are at least CLD) to contribute, whilst retaining change history etc. In addition, developers can choose to use something like CommitMonitor to automatically keep their reuse library up to date (helping address #1).
With the user.lib and instr.lib locations, this has been working like a charm and the Templates folder was the next target on the list for the expansion as some reuse elements are designed to be customized, and needed to be more of a complete VI than a Merge VI (e.g. a dialog box requires controls to be specifically located as well as block diagram code). It was at this point that I tried creating a versioned sub-fodler within Templates, found the issue, and came here.