You don't need to remind me of anything, the problem is that we don't own the 
code for voiceover. We only own the code for Growl. I mean own as in the people 
who can look at it and fix things. Since I cannot reproduce it, I cannot debug 
it. Looking at your environment isn't going to do much good in this scenario, 
reproducing it in mine is going to. 

If I cannot reproduce it but your friend can, and everyone else who has 
voiceover on (I guarantee it's more than 2 people) are not complaining, then 
we're at an impasse. My thought to send you to the apple store was because I 
can't think of another option. Nobody on the list has tried to reproduce the 
issue and actually said they saw the issue occur, which to me is pretty odd 
since we have some really helpful people on this list. So either they're too 
busy to try, or nobody was able to see the problem.

So to me that means that maybe you have something that none of us do. Some 
custom voice maybe, or some setting that you and your friend share that I just 
don't have. I have no other data to go on except the fact that you can see the 
problem, and I cannot, and your friend can. That's it. That's not enough to go 
on since there is no crash log and no logging in general.

So to answer your initial question, no, this is not going to be "fixed" in 2.1. 
It likely will never be fixed unless the above situation changes, since if we 
cannot reproduce it we cannot fix it if we have no other logging. Frankly I 
feel for you, don't get me wrong here. I just don't have another option at the 
moment. If something changes, i.e. anyone on our core team can all the sudden 
reproduce it, or you and your friend actually find some useful logging for it 
or something missing from the reproduction steps, let me know. Otherwise this 
is likely where this issue is going to stay, in limbo. 

-- 
Chris Forsythe
@The_Tick (http://twitter.com/The_Tick)


On Saturday, March 30, 2013 at 7:06 PM, BBS wrote:

> Well if someone would like to add me on Skype with the username 
> bbstheblindrapper, I can show you what happens. As for the comment about 
> there something being wrong with my Mac, I'd like to remind you that this is 
> happening to my friends as well and they have newer MacBooks than I do.
>  
> Shawn
> Sent from my white MacBook 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Growl Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> (mailto:[email protected]).
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> Visit this group at http://groups.google.com/group/growldiscuss?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Growl Discuss" 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/growldiscuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to