On 2009-01-18, at 03:08, Spike Spiegel wrote:
> any ETA for 1.3 …?
No.
> And if it's a problem of priorities and lack of resources any chance
> someone could take a stab at pointing me toward the right direction
> so I can try to fix this myself?
Sure:
http://growl.info/documentation/developer/growl-contributor-handbook.php
For a one-off patch, you can ignore all the parts about Bitbucket. (As
it is, I am debating removing them entirely from the Contributor
Handbook.)
The solution is to switch away from the SystemSound API to QTMovie,
with a QTAudioContext for the alert sound device. The reason I haven't
done this is because keeping track of the alert sound device is
tricky; Adium uses this approach, and there's an Adium ticket with
instructions on making Adium lose track.
(Note: Please don't copy any part of the Adium code. It's under the
GPL, and if we include any part of that code, we would have to put
Growl under the GPL as well.)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
