Is there a way to display the SKILL functions being invoked similar to an excel macro?

 Hi Peter,

 One good way is to open your CDS.log file, much better with "tail -f CDS.log" so you can see the log being displayed like in real time. But As for me, I prefer to search in cadence SKILL pdf files for functions because the first method I think can only help you with interactive functions. The pdf files are already sorted depending on the nature of the function e.g design framework, composer, layout editor, techfile, etc. so it is easier and informative.

BR -lrlsk

Of course, there's no need to use "tail -f" on the log file - you can use the Options->Log Filter settings in the CIW to control which bits of the log file get displayed in the CIW.

However, as Irlsk says, these primarily log the interactive interactions - which is fine in some cases, but otherwise you might want the procedural equivalent of a function - so for example, you might see deNewCellView() but in your program you might not want a window at all and so dbOpenCellViewByType() might be more appropriate. Such information won't be shown in the log file (or elsewhere), so searching the documentation (using cdnshelp is probably easiest) is the way to narrow down the functions needed. Or using cdsFinder to search for functions based on words that are in the function names.

Best Regards,

Andrew.

Great, thanks guys

 Hi Peter,

Just in case you were not aware, the cdsFinder or "SKILL Finder" tool can be started from the CIW either from the menus Tools -> SKILL Development -> Finder, or by typing "startFinder()", or from theUnix prompt by typing cdsFinder.  It can be a bit of a guessing game sometimes, so you might need to try parts of a possible function name, for example, related to your case you might try "open" or "create" as part of the function name.  Also, if you have a copy of the SKILL Quick Reference Manual, this can be helpful to browse through, and the functions are organised into sections for a particular tool or function class, e.g. Schematic functions, Core SKILL functions. 

If you know the tool that you are working with, for example Schematics, you might guess that the function name begins with the "sch" prefix, or "le" for the Layout Editor, "db" for generic database functions, "ge" for generic graphics editor functions, "hi" for Human Interface functions (forms, menus, bindkeys etc.)  This approach does not always work, for example the function to open a cellview non-graphically is a db function rather than, say, an "sch" prefix function or "le" prefix function.  Another example might be selecting an object in a schematic (or layout) window; there are some "ge" prefixed functions for selection which are not tied to which tool is being used (symbol, schematic or layout windows).

I hope that this helps.

Best regards,

Lawrence.