blah blah...you know what you said. (:-)
I've tried using 2 macros with a <foreachmember> loop in the first,
calling a second one with a <forN> which iterates each second level
member. However the <setlocal>/<getlocal> pairs coupled to an
<append> in the first macro recombine the data into the original
form, even though the within the macro everything is separated as I
want them to be
The results are written from a Perl script, so if changing the
structure of DX file there is a better way to go than doing it
inside DX that is possible.
Unfortunately, there is a limit to mow many field can be displayed
in a <selectorlist> so I cannot just write all my FE data fields
(upto 20) for all my element groups (often 20+) into a flat file.
Since that exceeds the limit (and makes for really huge data sets to
visualize).
Thanks for your time
Peter
Here's a good case wherein not to use the default member numbers.
There is no guarantee which member will correspond to which number.
Instead, establish a string-based naming convention. This presupposes
each main group has the same family of members. Assuming that's so,
you can simply Select(0) (member 0) of the Main group to send to
Selector to initialize its string values for the user to pick from,
then send Selector's string output to the macro described below along
with the MainGroup.
Then, as you did, ForEachMember("main") yields each subgroup, so you
should be able to trivially Select("named-member") and Append to a
new group which has been seeded with a null CollectMultigrid or
CollectNamed fed into the GetLocal to initialize it. I don't see any
need for a nested ForEachN.
If all top level groups don't have all the same-named members, you'll
need Inquires and stuff to do some error-trapping. Probably easier
to pad all top level groups with null but named members.
--
Chris Pelkie
Scientific Visualization Producer
618 Rhodes Hall Cornell Theory Center, Cornell University
Ithaca, NY 14853
