Misc / AVSTrans Automation greatly enhances the syntax of the AVS coding
language, simplifying the work with megabuf, loops and ifs and many more!

After activating the "Enable AVSTrans Support" checkbox you have access to a
number of new possibilities including:
 - writing code as parameters of functions (like loop() or if())
     Example:
     -----------------------------
     if(above(a,b)
       pn=0;
       loop(n,
         assign(megabuf(pn),a);
         assign(megabuf(pn+1),b);
         pn=pn+2;
       );
     );
     -----------------------------
       
 - using megabuf on the left side of an equal sign
     -----------------------------
     Example:
     if(above(a,b)
       pn=0;
       loop(n,
         megabuf(pn)=a;
         megabuf(pn+1)=b;
         pn=pn+2;
       );
     );
     -----------------------------

 - use automatic replacements that are done before the code is compiled
   (much like macros in C/C++, except that these replacements count for the
   whole code)
     -----------------------------
     Example:
     #define xp megabuf(pn)
     #define yp(a) megabuf(a+1)
     if(above(a,b)
       pn=0;
       loop(n,
         xp=a;
         yp(pn)=b;
         pn=pn+2;
       );
     );
     -----------------------------
   
 - include external text files. the #include (up to the end of the line) is
   replaced with the given file name.
     -----------------------------
     Example:
     #include vectorfoo.hvs
     c=scalprod(a,b);
     -----------------------------

You can also put the #defines and #includes into the "Global code" edit box of
the config screen to have them autoprefixed to each and every code block in the
preset. This will save you a lot of typing and make your code look a lot nicer.

The APE also contains a code logger. It logs all of your code to the specified
directory (default is C:\avslog). The components are numbered in the order of
their first compilation (that usually means the tree from top to bottom). Four
different log files are made for each component. Usually one for each code box.
Some components don't have 4 code boxes. For these components, the log file
names are undefined. This means they are all present but you probably have to
look through all of them to find what you're looking for :)
The log path is saved in avs\eeltrans.ini