> Yes, I'm fully aware of the string conversion functions.
>
> I was trying to avoid have to individually wire each and every cluster
> element to a seperate conversion functons or an array -- if possible.
> I wanted to simply send the cluster directly to a fle in ascii format.
> So if I add or delete any cluster elemtes, I dont have to go and find
> the format converter, and either have to add/modify/delete it.
>
The point I was trying to make was that those string conversion
functions work on clusters and arrays of numerics. Rereading your post,
it seems that you have lots of data and don't have subclusters or
subarrays. Individual elements are always more difficult to access
since they are jumbled together. As others have mention
ed, the XML and
variant tools can do this in later versions by inspecting the datatype
in a general way, but in earler versions of LV, your can simplify your
task by having fewer scattered elements in your cluster -- putting the
numerics together and the strings together. This will allow for
unbundling and string formatting the fewer big pieces. For unique
pieces where you want the name, you will still need to revisit the
printing code as the type changes, but you will not need to for adding
another channel value.
If you are stuck at 5.1 and really really want this functionality, the
flatten to string gives you what is essential, but it is necessary to
dig through the External Code Reference Guide, or the CIN reference
manual or whatever it is named these days to determine your control
names and types. It is also possible to do this with control
references, but it is almost as tricky, and I don't think you have those
classes in your palette.
Greg McKaskle
