I would like to use Orcad Capture TCL scripting. Before the 1st hotfix of 16.3 the command window in Capture echoed all of the operations performed during the editing session. Also .captcl session script log file was available as it is written in the manual. Since 1st and till the 7th hotfix neither command window echo nor .captcl session script log fileare available, and this was my ultimate source of examples.
What can be done to get both features back? (Apart from uninstalling all of the hotfixes.)
BTW, I use Win7/64 and tried to run Capture as administrator, if this info may help.
I think the logging option was turned off to increase performance.
If I remember correct you can turn it on again
1. View->Toolbar->Command Window
2. In the command window write "SetOptionBool Journaling TRUE"
Try this out and let me know if it works out for you (NB: You'll probably have a line with that option set to FALSE in your Capture.ini file.)
Thank You very much, Your suggestion works. The capture.ini configuration option is called just "Journaling". After all, it would be good to see all this described in manual.
We are trying to turn off the Input arrows on the schematic that is new with OrCAD 16.3. We have tried the command with no success:
SetOptionBool DrawPinArrows Off
We get back the following message:
SetOptionBool <Option> < TRUE | FALSE | ON | OFF | 1 | 0 >. Option can be one of: RotateInstPropInContext ViewerShowPinInfo FlushImmediate Journaling
It appears this is not a valid command.
I think that the option may only have been enabled after applying a hotfix, if you are running a base release, this setting may have no effect. As an alternative, try the Capture.ini file, usually alongside Capture.exe in the installation, close Capture before attacking this, there will be a "DrawPinArrows" entry in there, in the Preferences section, True is the default value, set the text value to False, save the changed file, restart Capture and see if that makes any difference, if not, you may need an update (hotfix) applied.
Well.....that certainly fixed it after updating with the latest hotfix.
Thanks for the tip!