On Mon, 19 Apr 2010 07:47:10 -0700, Alan Coopersmith
alan.coopersm...@oracle.com wrote:
Where the above approach would work is on the first EnableDevice() for this
device - this is guaranteed to be the first attachment and the one where we
may change the bell volume based on the MD.
Peter Hutterer wrote:
Why not have the slave inherit the volume level of the master when it is
attached?
Careful here - a client may change the bell on just one device and detach it
(or implicitly detach with a grab). In this case, the device shouldn't
inherit the bell volume from the
So, I've finally read through this and I'm still not sure what the right
solution is, but here are my 2 cents.
The real problem is the growing divide between Core and XInput.
The VCK should not result in an audio beep as it is a virtual device.
ProcBell should iterate through all physical
On Sun, Apr 18, 2010 at 11:48:49AM -0700, Jeremy Huddleston wrote:
So, I've finally read through this and I'm still not sure what the right
solution is, but here are my 2 cents.
The real problem is the growing divide between Core and XInput.
The VCK should not result in an audio beep as it
Yeah... I was seeing this as well. I brought it up last month:
http://lists.x.org/archives/xorg-devel/2010-March/006265.html
And ended up just letting core ring it (DDXRingBell):
http://cgit.freedesktop.org/~jeremyhu/xserver/commit/?id=eac7cdabecafb7c505795207182ab2578d672c06
I don't have a
On Fri, 16 Apr 2010, Alan Coopersmith wrote:
Several users have complained to me about their X server bells on
recent builds of OpenSolaris - definitely with Xorg 1.7.x releases,
I don't know if it affected Xorg 1.6.x before that as well.
The complaints I've gotten are two-fold: the bell
