Due to a change in the way ListSTAR responds with the path to itself you may experience problems with your ListSTAR 1.0 scripts. In all of the 1.0 demo scripts (script.return Recipes/Digests + script.create Recipes List/Digest List) there are two lines in the script which create the path to the ListSTAR folder (this occurs once per script). They are:
set strStart to path to me set strListSTARpath to text from character 1 to character -16 of (strStart as string)
The set strStart to path to me command actually asks the finder for the path and it returns "<Hard Drive>:ListSTAR/SMTP:ListSTAR Server" (if using ListSTAR/SMTP). The
set strListSTARpath to text from character 1 to character -16 of (strStart as string)
command would then strip off the ListSTAR Server part leaving "<Hard Drive>:ListSTAR/SMTP" with which all other paths are built off of.
In 1.1 we added a "path to" command in ListSTAR which returns just "<Hard Drive>:ListSTAR/SMTP:". There are times when a script is executed that the Finder is not asked the path to command and ListSTAR is giving its response - "<Hard Drive>:ListSTAR/SMTP:" the
set strListSTARpath to text from character 1 to character -16 of (strStart as string)
command then strips off ListSTAR/SMTP which then ruins the paths for the script.
To correct this go into the scripts that were shipped with 1.0 and look for the lines
set strStart to path to me set strListSTARpath to text from character 1 to character -16 of (strStart as string)
and replace them both with
tell application "ListSTAR Server" set strListSTARpath to Path To end tell
That should correct any problems that may occur with the 1.0 demo scripts that require paths to the ListSTAR folder.
StarNine Web Site | ListSTAR 1.1 Information Directory | ListSTAR Product Information