Change the Channel Create SCP Receive instance to include creation and destruction of the File Info object

[volks73]

The Channel Create SCP Receive instance is kind of awkward to use. A File Info object must be created the Channel first, then the remote file size is obtained and then the File Info object is destroyed. See:

It just looks messy. I think this was done originally because the polymorphic selector was hidden, so the instance controls could not be similar to another instance for the automatic selection to work properly. Now that the selector is visible by default, I think this need is removed and the File Info creation, usage, and destruction can be wrapped into the SCP Receive variant.

However, there are a couple of concerns:

• The above implementation is explicit and there is no magic involved. This is consistent with the library in that it is explicit and low-level in nature with the intention of a higher level API to be created around it.
• While in the above snippet and file download example only uses the file size, the other member fields of the File Info object, and ultimately C struct, might be needed for other applications using a SCP Receive-style channel. This issue could be mitigated by getting the values for all of the member fields and returning a cluster of the File Info from the Create SCP Receive instance. This seems reasonable as the File Info object/struct is essentially "read only".
• Related to the previous issue, are there implementations or usage that I am not seeing where breaking out the File Info creation, usage, and destruction are needed?

[volks73]

As of 588dbb130c47bb3f6ea07ef397f77f394e617d8c, the Create SCP Receive VI uses an internal File Info object and returns all of the file information as a cluster. This greatly simplifies creating a SCP download-like VI.