On Oct 5, 2009, at 9:58 PM, David Berry wrote:
>
> What could work though, is if kpg1_grgrp was to store the concatenated
> list of elements using a different parameter. So if kpg1_gtgrp is
> called to get a value for parameter "CONFIG" (for instance), it could
> store the list of group elements as the current value for parameter
> "CONFIG_V". It would need to create an IFL entry for each such "_V"
> parameter. Presumably it could call PARSECON_NEWPAR to do this, like
> you did for MSG_FILTER etc. When the NDF is closed, the NDF library
> would store values for both CONFIG and CONFIG_V in the history record.
>
> Does that sound any good?
Yes. We just want the data in the HISTORY so new hidden parameters is
fine with me. We don't want to parse it back or put it in as a default
prompt (the current scheme is great for that).
--
Tim Jenness
Joint Astronomy Centre
|