--===============0604477220==
Content-Type: multipart/signed;
  boundary="nextPart7896462.Dbdmq8Dd7W";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart7896462.Dbdmq8Dd7W
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello,

I think I have to shed a bit of light onto the System bell mess:

The mess comes from the fact that we have two "bells" and two different=20
options in two different KCMs that do something different but sound=20
similar if you think that we only have one bell.

One "bell" basically is KNotify. This bell receives all events from the KDE=
=20
applications. The other bell is the system bell, which gets used as a=20
low-level notification mechanism by the X-Server and a number of non-KDE=20
applications.

The setting in the "Sound & Multimedia -> System Bell" module is used to=20
get KNotify use the system bell instead of its homebrew own notification.=20
(OK, most of the time we want to have the homebrew own notification, but=20
if the computer does not have a soundcard we might want to get system=20
beeps instead.)

The setting in the "Regional and Accessibility -> Accessibility" module is=
=20
used to configure the effect triggered by the system bell. Here you can=20
decide to activate a visible bell or play some sound file instead of (or=20
in addition to) the system bell beeps.

> > > On Sunday 27 February 2005 4:42 pm, George Staikos wrote:
> > > > The whole system bell concept seems to be very broken right now.=20
> > > > The accessibility module is overriding KDE settings and making
> > > > things very confusing.  How do we fix this properly?
> > > [...]

As far as I know (but I did not test it, though) the two options are=20
working perfectly if you have configured them correctly.  Maybe the=20
background is too obscure to be understood without the explanations I=20
wrote above. In that case we need to make it more easy understandable (I=20
do not know if that is possible for KDE 3.5 or if that requires BIC=20
changes)

> > On Monday 28 February 2005 04:34, Benjamin Meyer wrote:
> > > According to the TODO file in kcontrol the one in Sound And
> > > Multimedia is slated to be removed for 4.0 when we are allowed to
> > > change stuff.

I am happy to see the option removed if "Use the system bell" becomes a=20
possible response for each KNotify event individually. We do not want to=20
always use the system bell, but some users might want to hear the system=20
bell for certain events (especially with a broken sound card).

> On Monday 28 February 2005 03:17 pm, George Staikos wrote:
> >   Ok, but breaking it instead of removing it is hardly acceptable
> > behaviour. How do we fix this situation?  Remove the one from the
> > accessibility module temporarily?  Make them cooperate?

Removing the option from the accessibility module is not an option if you=20
have read my explanation above. We have to make the two options cooperate=20
with each other and we need to make clear to the user that there are two=20
"bells".

On Monday 28 February 2005 12:23, Gary Cramblitt wrote:
> I have 4 SystemBell settings in my config directory:
> [...]

We do have multiple entries called "UseSystemBell" because some=20
applications allow to bypass KNotify in order to use the System Bell=20
instead. I would like to see that cleaned up for KDE 4 (if KNotify=20
supports using the system bell by then).

> Note that "kcmshell bell" is the same as Control Center -> Sound &
> Multimedia -> System Bell.  So this appears to be a bug.

I do not see a bug in there. With "kcmshell bell" you open the "Sound &=20
Multimedia -> System Bell" KCM just as you use "kcmshell kcmaccess" in=20
order to open the "Regional and Accessibility -> Accessibility" KCM. Or do=
=20
you think that it should read "kcmshell kcmbell" instead?

> There is also code in kdebase/kcontrol/accessibility/accessibility.cpp
> that seems to read from a "bellrc" file.  Is this code active anymore?

This code is not active and to my knowledge it has never been active.=20
Pupeno started to rewrite the Accessibility module=20
(kdebase/kcontrol/access). However, instead of starting in kdenonbeta he=20
directly started it in kdebas/kcontrol/accessibility (or am I wrong=20
here?). The rewrite was never finished and in the meantime I have extended=
=20
the functionality of the old module in kdebase/kcontrol/access. I do not=20
know whether updating the rewrite or starting the rewrite from scratch is=20
less work.

> There is also code in kdelibs/kdecore/knotifyclient for UseSystemBell,
> but I'm not sure which rc file this reads/writes (application specific?)
> or how one changes it in the gui.

If you are referring to the static function useSystemBell() in the=20
namespace KNotifyClient, that function returns true if "Sound & Multimedia=
=20
=2D> System Bell -> Use system bell instead of system notification" is=20
enabled Basically the KDE applications should then use the system bell=20
instead of KNotify (but I expecht that this is already handled in the=20
knotifyclient.cpp file).

> The setting under Sound & Multimedia -> System Bell is labeled "Use
> system bell instead of system notification".  Is this really the same
> setting as under Regional and Accessibility -> Accessibility, which is
> labeled "Audible Bell / Use system bell"?  The former implies it only
> affects KNotify stuff.

The two are very different settings. With the first setting you bypass=20
KNotify and trigger a system bell event which perhaps gets interrupted by=20
the kaccess deamon. If so, then the kaccess daemon will maybe start some=20
visible bell. It will also stop the event if the second setting is=20
disabled or ring the bell if it is enabled.

> Is everyone else as confused as I am. :/

This question can either be answerd with "No" or it will stay unanswered as=
=20
one person who is not confused is enough to say "No".

At least I do perfectly know what is going on here.

Gunnar Schmi Dt
=2D-=20
Co-maintainer of the KDE Accessibility Project
Maintainer of the kdeaccessibility package
http://accessibility.kde.org/

--nextPart7896462.Dbdmq8Dd7W
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCI7uEsxZ93p+gHn4RAn0TAJ46dZDHL23ZuZdmLia1MoX+i3kawACgzSK5
jenFSDzqvt17PQDbYb+qWa4=
=IGCA
-----END PGP SIGNATURE-----

--nextPart7896462.Dbdmq8Dd7W--

--===============0604477220==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-accessibility mailing list
kde-accessibility@kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility

--===============0604477220==--