Yes, I know of the structure decoder for LV4, and I know I run into trouble
with new versions of LV, but it is in fact very easy to decode the LV
structures (LV4 version was unecessary complicated).
So why am I doing this?? Since I am building large signal processing
applications with LV, there is a lot of work to write the code for storing
configuration files when a large number of variables are involved. The
appliaction uses global variables (again I am aware of the discussions of
were to use globals or not) to store sttings for a signal processing block
(often 2- 10 variables) and in the application I now have some 20 different
signal processing blocks. I use a cluster to hold the variables for each
block, and with the new VI I just pass the vi recerence of the signal
processing module ( module often uses 2 - 5 blocks, and therefore 2 - 5
clusters) and all this information is written to a configuration file. I
tell you that I save a lot of work writing new modules now. From this
decoding VI I also get a string that looks like the configuration file, and
this is passed to WORD as text together with the results from the signal
processing. In this way I get store the actuall settings used during that
particular analysis. ....and again I save the time to write the code to
store each parameter to WORD. You shold try it.
May last message two days ago, I said that only U32 was decoded, one day
later I can write and read all LV variables including complex numbers and
numbers with units to and from configuration files. (Arrays are not suported
sice i do not like them in config files). Since I have used the underlying
configuration file functions in LV51, it is fully copatible with those
functions.
I think that decoding of these structures should be implemented in LV so we
dont have to bother with changing internal LV structures!!!!
See attachment
Hans ?hra
Jean-Pierre Drolet skrev i meldingen <384816a7@newsgroups.ni.com>...
>There is a structure decoder for LV4
>
>ftp://ftp.pica.army.mil/pub/labview/vi/lv4/lv-structure_decoder.llb
>
>that does what you are trying to do for LV5.1.
>
>So much work became obsolete the day LV5 was released. So my advice is not
>to spent too much time on VIs that depends so strongly on the LV data
>structure, which is 100% guaranteed to change in the next version.
>
>If you really want to you can try to upgrade the LV4 structure decoder to
>LV5.
>Maybe a good shorcut would be the 4.x to/from 5.1 data format converter
>found in the LabVIEW
>support files:
>"vi.lib\utility\victl.llb\Convert Type Descriptor and Flat Data.vi"
>
>Regards
>
>Jean-Pierre Drolet
>
>
[Attachment Outer Cluster.doc, see below]