On Tuesday 13 January 2009 09:01:03 Tim Mooney wrote:
>
> Autosave (v 4.3 and later) does already permit info nodes to specify the
> fields that are to be autosaved. However, I have not found a way to
> make vdct leave these fields in a database.
This doesn't solve the issue with vdct remembering info data (the ability to
do so will have to be coded into vdct; if someone needs this and is willing
to pay for it, I'm sure CosyLab will be happy to oblige), but you can at
least put the info data into a separate file.db that just contains entries
like these:
record(type,name) {
info(key,value)
...
}
...
It wouldn't be hard to write a tool to pull just these items out of an
existing .db file into a separate file; ask me if it would help and I'll see
what I can do.
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- Replies:
- RE: Vdct and autosave's info field Thompson, David H.
- RE: Vdct and autosave's info field Alarcon, Arturo
- References:
- Vdct and autosave's info field Alarcon, Arturo
- Re: Vdct and autosave's info field Tim Mooney
- Navigate by Date:
- Prev:
Re: Newport ESP300 on Linux Ron Sluiter
- Next:
Re: webca can't connect to pvs? Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Vdct and autosave's info field Tim Mooney
- Next:
RE: Vdct and autosave's info field Thompson, David H.
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|