Cosylab has upgraded VDCT, starting with v2.6, so that the info field is kept after resaving a VDCT file, using VDCT, that has info fields included.
arturo
-----Original Message-----
From: Andrew Johnson [mailto:[email protected]]
Sent: Tuesday, January 13, 2009 8:20 AM
To: [email protected]
Cc: Tim Mooney; Alarcon, Arturo
Subject: Re: Vdct and autosave's info field
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
- References:
- Vdct and autosave's info field Alarcon, Arturo
- Re: Vdct and autosave's info field Tim Mooney
- Re: Vdct and autosave's info field Andrew Johnson
- Navigate by Date:
- Prev:
Re: ADEL field in motor record Ron Sluiter
- Next:
ca examples Patrick Thomas
- 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 Thompson, David H.
- Next:
Newport ESP300 on Linux Patrick Thomas
- 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
|