The subject line pretty much says it all -- if you have an Automator workflow running which uses the Growl notification action, and Growl happens to be off, the whole workflow crashes and throws up an error to the user. No way this is the most elegant behaviour possible.
I understand sometimes it can be desirable but can we at least have an option in the workflow to silently treat the action as a no-op if Growl is off? Should be really easy to do. Otherwise people are just going to ignore this action and insert a shell script instead which does the check. Would you guys take a patch for this? -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
