This is an issue we have thought about in the past without doing much on
that score. The main problem is what does it mean to copy a peak list,
for example do resonances, etc., get copied, or only peaks and their
positions. I started to write some code which allows you to copy an
"oldObject" to a "newParent" which only follows parent child links (e.g.
Peak to PeakDim) but not "cross" links. However we just noticed that the
peakContrib to peakDimContribs link is a cross link and one would
certainly want that copied. The problem with trying to copy cross links
generically is that you can end up copying the whole bloody tree, which is
probably not intended. So it's possible this generic copy will never work
and we'd need to write specific copy code for peak lists and specify
fairly carefully exactly which links get copied and which do not.
On Wed, 13 Oct 2004, Huw Jenkins wrote:
> Is there any way to export an analysis peak list from one project and then
> import it into another project?
> If not it seems like a useful feature...