Quote:
Originally Posted by whpalmer4
Obvious first thing to check would be that you have a top-level context with the same name that the script is expecting. There's a property definition near the top that seems to supply the name, but in fact the script doesn't use it, doesn't handle the case where the context doesn't exist in any way, and doesn't handle a context which is nested inside another.
|
The original script used this property, but the script posted by @bugvi is missing the code that references the property. A quick glance of the script shows this:
Code:
set theContext to context "Waiting for ..."
which bypasses the property that is intended to be set in the myWFContext statement. Who knows what else is now broken in this script?