An Altium scripting walkthrough using both VBScript and Delphi, with guides, API info, examples, links to 3rd party scripts and more. Look at most relevant Altium scripting examples download websites out of 1.54 Million at KeyOptimize.com. Altium scripting examples download found at code.google.com.

BEFORE YOU WATCH – the purpose of this video is to provide a very high-level overview of scripting in Altium Designer. This is not a “how to”. Eiklor Control Valve Manual.

It provides you an overview of what you will need to know going into this effort. Unfortunately, this is not a trivial effort. Along with this video, please consider the following commentary: Many high-end tools offer the ability to script. It is a feature that intrigues most engineers who are always looking for a way to automate something.

Embarking on a script, especially one that has to do with evaluating the position of primitives is much like writing a novel. It may be exciting at first, but it can take a good deal of time and enthusiasm to get it up and running. More often than not, though we have the interest, work obligations get into the way. For example, if I can repeat of key clicks and mouse motions 100 times and can do it in 5 minutes, am I willing to invest 20 minutes researching whether a feature exists and more so, how to use it? Am I also willing to invest 1 or 2 hours if this is something that needs to be coded?

If mashing a bunch of keys and mouse clicks dozens of times is a one-time proposition, then most of us just grin and bear it. If we have to do it again at some time in the future or if we know that our colleagues also partake this particular manual effort, then we may consider the other options. This question was posed to one of our experts in Altium scripting. As if scripting was not difficult enough, Altium makes it more difficult by not providing all the processes and their options.

When someone approaches Nine Dot Connects about a script, it is carefully reviewed to ensure that it is viable option. As for whether one should pursue a script, consider one or more of the following criteria: • Does it meet (a) specific need(s) which typical users believe is needed but with which they have difficulty either remembering or implementing without making mistakes? • Does it significantly speed up processes done regularly and thus saves a lot of time?

• Does it implement a process which is too manually complex, obscure or esoteric such that the user has trouble remembering how do it? • Does it implement a feature which is too complex (computationally or otherwise) for the user to do manually? • Would it be simple and fast such that it saves way more time that is takes to use it? A good script is more than pressing a run button.

It needs to provide feedback. It should have control and reporting dialog boxes to confirm it is being run, allow the setting of options, and summarize immediate results. And, if the script is going to be sold, it needs to provide much more value than it costs to invest in the tool. In all cases it must not conflict with procedures a company has already established (such as file naming and storage protocols, configuration managements, etc. Browser Based City Builder Games. ). It also must be something which is done fairly regularly so the user does not forget how to use it.

For example a script to draw schematic templates (with borders, zones, title block, parameters, fields, section indicators, different sheet sizes, top vs. Doom 3 Bfg Edition Invincibility there. Continuation sheets, logo insertion, etc.) could be really nice for a design service, but not of a lot of value to a customer at one company who would only do it once. It would be of little value it its sole purpose replicated an intrinsic function of the tool, such as checking for connectivity. It is much safer to check and report on conditions than to modify or create layout because of the esoteric relations to other things.