Aegisub/automation/include
Niels Martin Hansen 8ffaf7cfa0 Missed something crucial from Classic Advanced skeleton
Originally committed to SVN as r1430.
2007-07-17 23:37:42 +00:00
..
karaoke.rb some useless Ruby scripts 2007-02-07 21:07:03 +00:00
karaskel-adv.auto3 Runtime errors in auto3 scripts no longer kill the program but are reported properly instead. 2007-02-06 12:30:17 +00:00
karaskel-adv.lua Auto3 engine for auto4 seems to work now 2007-01-18 08:15:02 +00:00
karaskel-auto4.lua Missed something crucial from Classic Advanced skeleton 2007-07-17 23:37:42 +00:00
karaskel-base.auto3 Well look. Automation 3 works now! 2007-05-07 13:38:12 +00:00
karaskel-base.lua Auto3 engine for auto4 seems to work now 2007-01-18 08:15:02 +00:00
karaskel.auto3 Auto3 engine for auto4 seems to work now 2007-01-18 08:15:02 +00:00
karaskel.lua Fixed some Lua 5.0/5.1 compatibility problems in includes 2007-05-03 18:22:11 +00:00
readme.txt Auto3 engine for auto4 seems to work now 2007-01-18 08:15:02 +00:00
unicode.lua Minor fixes to Lua includes. 2007-07-17 22:25:56 +00:00
utils-auto4.lua Minor fixes to Lua includes. 2007-07-17 22:25:56 +00:00
utils.auto3 Some extra colour handling code for Auto3, ported from Auto4/Lua. 2007-05-08 13:30:24 +00:00
utils.lua Fixed some Lua 5.0/5.1 compatibility problems in includes 2007-05-03 18:22:11 +00:00
utils.rb updated ruby scripts 2007-03-10 20:33:49 +00:00

readme.txt

This directory contains standard include files for Automation.
By default, this directory is included in the Automation Include Path, which
means the files here are always available for use with the include() function.

See the Aegisub help and the individual files in this directory for more
information on their purpose and contents.


DO NOT MODIFY THE CONTENTS OF THIS DIRECTORY OR ADD YOUR OWN FILES,

any files added or modified might be deleted or reverted upon upgrade or
uninstall of Aegisub.

A better solution is to create your own include directory and put it in the
"Automation Include Path" in the Aegisub config.dat file. The path
specifications are separated by pipe characters ("|"). Using this method, you
can also override the default includes with your own, modified versions, by
placing the path to your own versions earlier in the path list.