On Nov 30, 2010, at 18:39:41, jonhollander wrote: > I'm not sure what problems arise from using this script instead of GrowlMail > (as alluded to above); the script seems to work fine for me.
The script doesn't support summary mode as GrowlMail does, so if you get a whole lot of matching messages at once, you'll get buried in notifications. That said, I wouldn't expect more problems from using Mail's public scripting dictionary and support for scripts as rule actions than from using Mail's private undocumented plug-in interface. Quite the opposite, in fact. On Nov 30, 2010, at 19:00:34, jonhollander wrote: > In your previous message, you said: > >> OS X update. As it is I've almost thought of us changing GrowlMail to >> a script that gets added to a generic rule, thus sidestepping this >> whole cluster of not goodness. However, there are problems with that >> as well. > > I'm not sure what problems you were referring to in your previous message, > but if you could elaborate, perhaps I could change my script to address them. > As it is, the script works great for me. Among other things, either the user would need to add it to a rule or our Installer package would need to add it to a rule. The first would only be workable for advanced Mail users and the second would be very tricky to do without stepping on any of the user's other rules (and I wonder what Mail would do if the user uninstalled the script or migrated to a new machine that didn't have it yet—throw an error message?). -- 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.
