Hello,
We could in theory try to remember the exact state, including what was
open, etc. We haven't gone down that route (in particular the dialogs are
all closed on restart, just the open windows are remembered) because we
didn't think that literally everything should be remembered. So it was a
"feature" rather than an oversight. But we could try and go down the
exact-state route if people really wanted that.
We would like to avoid the ~/.ccpnmr approach. This would imply having to
come up with a new format and the point of the API is that we already have
a parser for free so why bother with yet another format which needs
parsing. On our TODO list is a "profile" ability which would allow people
to customise things a bit more easily than now.
Wayne
On Mon, 11 Dec 2006, Murali Vadivelu wrote:
> Dear Developers,
>
> It would be nice if analysis can remember the exact state it was in
> when you reopen a project.
>
> It would also be nice, if we have a set of system-wide or user set
> $env variables from which analysis picks up the path than from
> hardcoding it into the xml, which is so prone to errors, for example,
> if there is a change in the installation path, etc. A ~/.ccpnmr
> folder with some common settings would be great too.
>
> Many thanks.
>
> Best regards,
> Murali.
>
> On 11 Dec 2006, at 15:36, Stephen Paisey wrote:
>
> > Dear All,
> > Appologies for the double message but the same loss of memory as
> > mentioned
> > in my previous posting also applies to the "Link peak lists to roots"
> > function in the new release.
> >
> > Cheers
> > Stephen
>
|