> On 06/09/12 07:09, Johan R wrote:
> > I may be on thin ice here since i dont know the details of XBell which is 
> > used by fl_beep (fltk 1.3.0) on Linux but here goes:
> >
> > My new rig dont have a pc-speaker and i configured PulseAudio to handle the 
> > x11-bell.
> > I get bell sounds in my desktop (including xkbbell) but fl_beep in my fltk 
> > app doesnt produce any sound.
> > I suspect it is because fl_beep uses XBell and not a XkbBell function 
> > (which xkbbell use).
> >
> > Should fl_beep/XBell work ?
> > If not, any chance to improve fltk 1.3 to make fl_beep work ?
>
>       Sounds like a linux distro-specific issue, eg:
>
>       https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/231234
>       https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/486154
>
>       Yes, fl_beep() uses XBell() (see src/fl_ask.cxx for the code),
>       so if you can get XBell to work, fl_beep() will work as well.
>
>       Thing is, the above says this was deliberately disabled
>       by default because as someone put it, "too many applications
>       are abusing it (ie. bash_completion)".
>
>       So in other words, enabling it might drive you insane.
>
>       That second link seems rife with information; you'll likely
>       find a solution in there.
>
>       If not, let us know..

You might have misunderstood me, the PulseAudio x11-bell works fine for other 
apps (e.g. hitting backspace in an empty terminal).
After searching a bit i am pretty sure XBell will not generate the required 
event (XkbBellNotify) which is required to get the bell sound to a "sound 
card". I really think fltk should use XkbBell if available and only fallback to 
XBell as they do in xterm  (and probably most other apps) :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520405#15
http://anonscm.debian.org/gitweb/?p=pkg-xorg/app/xterm.git;a=commitdiff;h=5cc6c9ac6341aa3b67f68c5980c6d0349b5cfef0
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to