5 Replies Latest reply on Mar 1, 2015 10:57 AM by kendall_hiles

    Script Examples - AATK

    kendall_hiles

      Just a reminder that AATK has hundreds of scripting examples.  Most are vbs or forms but there are C#, JScript, TCL examples as well.  AATK is not just for Expedition, it has examples for CellEditor, Drawing Editor, Dx, Fablink, HyperLynx, HyperLynx DRC, Library Manger, PathFinder, Quiet Expert, CES....

       

      It is inteded as a template for creating you own menus, icons...  It has a general AATK section for slicing and dicing a design or creating automated output files and a specialized FlipChp section for more advanced features like importing and exporting data, data manipulation, net shorting...

      Currently we are updating AATK to make sure everything works with the new VX release. The only gotchas we have seen are scripts that deal with the display control since it is a new interface and scripts where we took advange of some Win32 functions that are not available on the 64bit build. I think we have crossed all those hurdles and if you want the VX build I could probably release a new build of AATK soon that will work from 2004.x through VX.x.

       

       

      You can download the toolkit off of the OpenSource website SourceForge.  All the scripts have source code and should be used at your own peril.  SInce we give you the source code, if something doesn't work, you can fix it to work yourself and then send me your fix and I will update AATK.  Our standard discalimer is we, especially Me, My team of contributers and Mentor Graphics are not held liable for anything whacky happening to your database!  We are really just trying to help so don't blame us for a delay or crash, these scripts are meant to help you do your job faster and better.

       

      You can donload AATK from here:

      http://sourceforge.net/projects/uwtoolbox/

       

      '  Acceptable Usage Policy

      '

      '  This software is NOT officially supported by Mentor Graphics.

      '

      '  ####################################################################

      '  ####################################################################

      '  ## The following  software  is  "freeware" which  Mentor Graphics                      ##

      '  ## Corporation  provides as a courtesy  to our users.  "Freeware"                      ##

      '  ## is provided  "as is" and  Mentor  Graphics makes no warranties                    ##

      '  ## with  respect  to "freeware",  either  expressed  or  implied,                          ##

      '  ## including any implied warranties of merchantability or fitness                        ##

      '  ## for a particular purpose.                                                                             ##

      '  ####################################################################

      '  ###################################################################

        • 1. Re: Script Examples - AATK
          Patrick.Cashman

          Thanks to Kendall and the team for providing the AATK and all thw work that has gone into it.

          • 2. Re: Script Examples - AATK
            kendall_hiles

            Thank's Patrick!

            • 4. Re: Script Examples - AATK
              derrick.xu1

              Hi Kendall,

              Could you give me the detail install method for AATK? I have set up the environment as read me.txt said, but it seems can not work in Expedition.

              • 5. Re: Script Examples - AATK
                kendall_hiles

                Extract the directory somewhere and call it what you want, lets say C:\tmp\FRED  If you look in FRED, you should see the scripts.ini file.  That is the file that loads the user ware for each tool.

                 

                Create an environment variable call AATK and set it to C:\tmp\FRED  This allows one script to call another..

                 

                For Expedition  add C:\tmp\FRED  to the WDIR env variable

                For Xpedition add C:\tmp\FRED  to the WDIR_EEVX_1 env variable

                for any new release it will be the WDIR that is set during the install of that tool.

                 

                The first path in the WDIR or WDIR_EEVX_1 is where the tools dump all the outputs so I usually add the AATK path as the second item in the path.

                 

                Most common mistakes people make are:

                1. Misspell the path

                2. Added a : instead of a ; between the paths

                3. Added a space in the env var somewhere

                 

                To add/change environment variables, I use RapidEE.  It is what Microsoft should have had all along.  It will allow you to edit your variables and will tell you when you have bad paths in your variables. I liked it so much, , I made a donation to the tool in September 2011.

                You can get it at www rapidee com

                1 of 1 people found this helpful