Schmye Bubbula wrote:
boredzo wrote:Until somebody comes up with either 100%-reliable steps to reproduce or a patch, this problem is going nowhere.
Is boredzo the developer?
You could just address me directly.
I'm the Lead Developer. We have other developers, but not very many, which is why our pace of development is so slow right now. I'm also the one who rewrote most of GrowlMail a few versions back.
I'm not a programmer, but it seems to me that things are too intermittent to come up with "100%-reliable steps to reproduce" the problem.
It happens 100% of the time for you, doesn't it? It works once, then fails thereafter, every time. What we need are instructions on how to make that happen.
Right now, the only instructions we have are “install GrowlMail” and “run the defaults commands [which are part of the installer]”, and neither one of those causes the problem for us, so we need to know what's different.
I don't know how to create a "patch," and unless I'm misunderstanding something (apologies in advance if I am), I would think that only the developer has the intimate knowledge of the program necessary to be able to patch it.
Growl is open-source. Anyone can download our source code, and any programmer should be able to read the GrowlMail source and to change it to include a fix. That change, exported to a file, is a patch.
Can't the developer do a little detective work?
I use GrowlMail myself. I have installed it many times, especially in working on the GrowlMail installer for 1.1.6. It still works. There's not much I can do besides try it on my own system, so if you want me to be able to help at all, you're going to have to suggest something to try.
The only other thing I can do is ask this question: Do you have any other Mail bundles installed? Check both Home/Library/Mail/Bundles and [your startup disk]/Library/Mail/Bundles.
We know the problems occur both in Tiger and Leopard. What code changed between v1.1.4, which worked flawlessly, and v1.1.5?
But remember, 1.1.5 works flawlessly (for us), too. We can back out commits all day and it won't do a bit of good if we can't reproduce the problem, because we wouldn't be able to tell which one had been causing it. Moreover, if the problem is something reverting Mail's Preferences (as it seems), then it really doesn't matter whether you use 1.1.4 or 1.1.5.
So there are only three ways this is getting fixed:
1. Somebody who can reproduce it tells us how to reproduce it.
2. Somebody who can reproduce it fixes it and sends us the patch.
3. Somebody who can reproduce it goes through the history, one commit at a time, to find the problem commit.
I'm not holding up 1.1.6 unless one of those happens. And anyone who starts on #2 or #3 should post here first, so I don't end up shipping 1.1.6 while they're working.