view doc/notify-signals.dox @ 12903:2bb4dc533a31

[gaim-migrate @ 15256] redpen686 posted modified sounds to gaim-devel: "The tones were sampled at 44.1 KHz (with a range of up to 22.05 KHz), which is fine, but since the tones are only up to ~3 to 4 KHz, a lot of space could be saved by downsampling. I went to 11,025 Hz, since it is already enough for these frequencies, and it's also the lowest common denominator for soundcards (rather than 8 or 16 KHz, for example). The 'alert' sound needed a lowpass filter, but only because of the high-pitched attack, which people won't notice anyway. All are still 16-bit, and in stereo (except for the 'alert' sound, which didn't need it), and so should sound virtually identical." These are significantly smaller files and I didn't notice a difference in the sound (of course, my speakers suck). They're also louder, which is good. I'm committing these so people can try them out. committer: Tailor Script <[e-mail]>

/** @page conversation-signals Notification Signals

 @signals
  @signal displaying-userinfo
 @endsignals

 @signaldef displaying-userinfo
  @signalproto
void (*displaying_userinfo)(GaimAccount *account, const char *who, char **infotext);
  @endsignalproto
  @signaldesc
   Emitted before userinfo is handed to the UI to display.
   @a infotext is a pointer to a string, so a plugin can replace the text that
   will be displayed.
  @note
   Make sure to free @a *infotext before you replace it!
  @param account  The account on which the info was obtained.
  @param who      The screen name of the user whose info is to be displayed.
  @param infotext A pointer to the userinfo text to be displayed.
 @endsignaldef

*/
// vim: syntax=c tw=75 et