Hello Alex, Automator, like AppleScript, requires the developer to build in support for actions or scripts. So Automator actions for functions that are not built into the operating system, like OCR functions, are installed when you loaded the application (e.g., Prizmo). Not all developers actions or scripts. A popular way to get around accessibility issues in early versions of Mac OS, especially before VoiceOver access to the extras menu came in Mountain Lion, was to check whether some software came with low level function calls that supported AppleScript.
>From the user point of view, Automator workflows are easier to set up, because >they don't require knowledge of AppleScript programming, and simplify the >repetitive execution of commands. However, Automator workflows don't let you >change your actions based on conditional decisions the way that AppleScripts >can (e.g., if this is true, then do this), or to iterate (e.g., while this is >true, do these things). Automator only lets you carry out a fixed sequence of >actions from an available action library. HTH. Cheers, Esther -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/groups/opt_out.
