Installation.

Place the 'Buddy API Xtra.xtra' file into the Director\Configuration\Xtras folder. Place the 'Buddy API.help' file into the system Help folder - /Library/Documentation/Help. Note that the Hep file will only work if it is placed in this folder. If you prefer, you can use the Windows Help file if you have a CHM viewer ( eg http://chmox.sourceforge.net) installed. In this case, place the 'Buddy API Help.chm' file into the same folder as the xtra.

If you are planning to also make Windows projectors, then place the 'baWin.xtra' file into the Director\Configuration\Xtras folder. Place the 'Buddy API Xtra.x32' file from the Windows Buddy API 4 download into the Director\Configuration\Cross Platform Resources\Windows\Xtras folder. Open the xtrainfo.txt file in the Director\Configuration folder and add this line to the bottom of the file:

[#namePPC:"Buddy API Xtra", #nameW32:"Buddy API Xtra.x32"]

The baWin.xtra file is a Macintosh xtra that contains all the Buddy functions that are Windows only, eg baReadRegString. This allows you to author the Windows only functions on a Macintosh system. The xtra itself does nothing and should not be distributed.

Changes in Version 4.06.

A "system" option has been added to baShell.
Options added to not show bundles in baGetFilename. 
The Copy functions did not copy symbolic links when using Unix names.
File names in HFS format can now contain Unicode characters and be longer that 31 characters.
baMsgBox and baMsgBoxEx now handles strings with accented characters correctly.
Various file functions did not work correctly with file names with accented characters when using HFS format names.
baDisableSwitching function added
Added option in baSysFolder to search specifically for User folders, eg: baSysFolder( "user library" )
baGetFilename when used with the "save" option, and returning HFS names, included a Unix folder separator