[Kde-accessibility] System Bell

[Olaf Schmidt-Wischhöfer]

Hi Peter,

how do you suggest to deal with non-KDE, console applications in this context?

Allowing people to see a “beep” printed by a console application seems to be a 
useful feature to me – for people who cannot hear, but also for broken audio 
hardware or intentionally silent (e.g. library) configurations.

I am not against moving the feature to a place where it suits better, but I 
suggest to be a bit cautious about completely removing an accessibility 
feature until we are sure that we have truly reached out to the people relying 
on it.

Best regards, Olaf

Am Montag, 12. Januar 2015, 00:10:50 schrieb Peter Grasch:
> Hello,
> 
> > On 06 Jan 2015, at 14:00, Heiko Tietze <heiko.tietze at user-prompt.com>
> > wrote: The survey about system settings did reveal some confusion about
> > the system bell (i.e. there was no clear association with other
> > settings). Most users do not even know what the system bell can be used
> > for (and even experts doubt to have the hardware). But there are still
> > people who want it for low latency audio feedback [1] and notification on
> > the console [2].
> I’m sure there are some users. But correct me if I’m wrong - none of the
> ones you pointed to have a real need for the KCM as it is now. (we already
> have low latency visual feedback regardless of a visual bell)
> > Nevertheless I agree with removing this feature or rather harmonizing with
> > default notification. As a notification feature you could bind the system
> > bell to some special activities, like console tasks. And disabled people
> > adjust notifications instead of accessibility, or both.
> A “beep” backend for KNotify would be nice and probably reasonably easy to
> implement. I think this should become a wish list item. Nevertheless, this
> imho shouldn’t block the removal of the KCM.
> 
> Best regards,
> Peter