> > We're working on a uuid patcher, that will read what the uuid is and then add > it to the growlmail configuration. We won't test, but so far the uuid has > been the only change we actually make, and then we run growlmail for 2 weeks > to test. > > There is a minor risk here, since everything that GrowlMail does inherently > isn't using a documented API. Meaning, that GrowlMail could make a call to > something that changed names and now it performs a different action. I don't > expect this, but it's still there. > > We could continue to play this game of back and forth updating, but it's > rather tiresome. Apple did this because some bad plugins were actually > crashing Mail. However, they could have created a public API instead and > avoided all of this mess.
Interesting, but a bit arcane for humble consumers like me. I'll hope you find a good fix. I certainly liked having Growl give me a heads-up on incoming mail. anmcl -- 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.
