This is kind of an odd idea, but I find that deployment issues often arise based around the right files being in the right places on the target PC. Whether it's remembering to include the files in the installer or failing to provide the right absolute reference to a file in a common location on the target PC that's used across many programs.
So when I first go to build an executable, or especially an installer, it'd be nice to have a handy way to just quickly look up all VIs in the source VI's hierarchy that can accept paths as inputs. I'm not sure how well this would work with any polymorphic VIs that also accept strings as inputs, but then convert them into paths. And I'm not sure how far into library VIs you'd want to drill. So maybe it's not very easily implemented. And maybe it's just a crutch for my own sloppiness.
Just throwing it out there.
Any idea that has not received any kudos within a year after posting will be automatically declined.