please help me to set an autosave option in 6.1.3 version?
I have tried to set
dbSetAutoSave(t 100) ,but it returns error connected with unrecognise
It seems that this version
is no longer support autosave option.
Is there no way to
The desigred result will be
the setting autosave with timing variables (for example to autosave the view
after each 10 minutes).
It is very important.
Are you sure you're using IC613? dbSetAutoSave() was not in the earlier versions of IC61, because it was not available in OpenAccess, but it was added in 184.108.40.2060.10, and is in all versions of IC613 (I tested the first version, 220.127.116.11 and the latest Hotfix, 18.104.22.1680.17). Note that the second argument is the counter increment between saves - a measure of the amount of change. Check Help->About in the CIW to see you really are using IC613. Can you post the exact excerpt from your CDS.log file which shows what you entered, and what the error was? I suspect you made a typo, if it said that "t" was unrecognized.
If you want a time-based auto-save, then look at Cadence Online Support Solution 11026354.
In reply to Andrew Beckett:
Thanks a lot for quick response.
We are using IC61.3.500.10 version for sure. You were right I’ve tried once
again with the new session of virtuoso and it does not give any Error.
You wrote: Note that the
second argument is the counter increment between saves - a measure of the
amount of change.
So, if I am not mistaken,
the number which was given to "t" will be a measure of the amount of
change? If it is so, what does it mean and how i can use it?
Unfortunately could not
register to online support site, maybe due to some issues with network. I will
try later as well, but if it is not hard can you please drop that solution into
Is it possible to contact
to the cadence support interactively (like in Yahoo messenger, etc.)?
In reply to shushan:
The first argument to dbSetAutoSave() is either t or nil. This means to enable or disable auto-save. The second argument is the increment in the modifyCounter attribute on the cellView which triggers the change. Each database change in OpenAccess causes the modifyCounter attribute to be incremented, and so the number you specify is the number of changes in the OA database which trigger an auto-save. Bear in mind that some commands in Virtuoso may actually make a number of database changes in one go. The meaning is therefore rather different to what it was in CDB, where the number was the number of change "chunks" that were made (effectively you could modify a whole chunk of things in one go, and it would only be counted as 1).
I don't want to post the solution code here, because Solutions are really intended for customers with support contracts. It's possible to contact customer support via email (email@example.com) but not via instant messenger. The reason being is that we give each request for service a "Service Request Number" and that is then tracked throughout the whole transaction. Most questions for Cadence tools are usually not just a trivial question which could be answered by a brief IM conversation - and also by using the Service Request approach, we can route the SR to an appropriate AE with the right skills for the product being asked about (as we have a very large number of different products).
This forum is not intended to be a replacement for Customer Support; instead it's intended to be a forum for the community as a whole to contribute and help out with suggestions and hints. It's reliant on the goodwill of all of those that contribute here, but for detailed customer support, you should go through the official channels.
Thanks,i'll try firstname.lastname@example.org,and Solution
11026354 as well.
The Error again appiars:
dbSetAutoSave (t 10)*Error* eval: undefined function - t
That's because you put a space between the function name and the open parenthesis. If you do this, it is interpreted as the same as:
which is not what you wanted - t is not a function. This is all to do with the fact that various syntaxes (C-like and LISP, to name but two) are supported in SKILL, and so if using the C-like syntax, you must not put a space between a function name and the opening parenthesis.
Miss out the space, and it will work.
Thanks a lot!!!!!!!!!
thanks for the answers..need it also..