I have attached a diagram of what we are planning at the moment. The functions ReadConfigFile() and WriteConfigFile() would be called when the user requests a load or save. The configuration data would be stored in one big structure.
GetData() returns a pointer to the structure, and is intended as the link between the PVs and the library.
> -----Original Message-----
> From: Johnson, Andrew N. [mailto:firstname.lastname@example.org
> Sent: Saturday, October 07, 2017 6:59 AM
> To: Iain Marcuson <Iain.Marcuson@sydorinstruments.com>
> Cc: EPICS Tech Talk <email@example.com>
> Subject: Re: Writing PVs from an amalgamated structure
> Hi Iian,
> I think we need to know quite a bit more about what you're trying to do, and
> where/when these configuration files will be read and/or written. The
> answers are likely to be very different depending on what you tell us, and I
> don't think anyone wants to spend time answering the wrong question.
> - Andrew
> Sent from my iPad
> > On Oct 6, 2017, at 6:22 PM, Iain Marcuson
> <Iain.Marcuson@sydorinstruments.com> wrote:
> > I need to create support for reading and writing a configuration file, but I
> also have to support non-EPICS environments. I am thus considering making
> a library to be used in the IOC. My present idea is to pass EPICS a pointer to a
> structure containing all the configuration options. However, I do not know
> what best practices are for mapping PVs to the memory location. What are
> the accepted methods?
> > Thank you,
> > Iain.