On Wed, Sep 04, 2013 at 02:25:02PM -0400, Jasper St. Pierre wrote:
Reviewed-by: Jasper St. Pierre jstpie...@mecheye.net
thanks for the review and the patch. merged into my tree, will be upstream
soon.
Cheers,
Peter
On Wed, Sep 4, 2013 at 2:09 PM, Thomas Klausner w...@netbsd.org wrote:
Keith, please pull this asap, Matt is waiting for the build fix for the 1.14
branch. Thanks. Thanks. Thanks. Thanks.
The following changes since commit 94d4e29aedc69431fa9b299ca1b67947173d7a24:
Xi: allow for XIAllowEvent requests larger than XI 2.2 size (#68554)
(2013-08-30 14:26:55 +1000)
I have my .xinitrc run xset -b to avoid most audio interuptions.
But have my window manager configured to give an audio alert when it
detect new mail in a certain mbox file. And that works.
Looking at the wm's src, I see that it just calls XBell(display(),100).
Based on XBell(3), it makes
On Wed, Sep 04, 2013 at 01:49:22PM -0600, Matt Dew wrote:
On 09/03/2013 11:45 PM, Peter Hutterer wrote:
On Tue, Sep 03, 2013 at 10:35:56AM -0600, Matt Dew wrote:
Ping?
I've merged this into my tree now, will be in the next pull request
Cheers,
Peter
Thanks Peter.
Any idea
On 09/ 5/13 02:44 PM, James Cloos wrote:
But I cannot replicate that in any other X11 client, including a simple:
#include stdlib.h
#include X11/Xlib.h
int main (int argc, char *argv[])
{
int vol = 100;
char *disp = NULL;
Display *display;
if (argc 1)
vol = atoi(argv[1]);
AC == Alan Coopersmith alan.coopersm...@oracle.com writes:
AC You need an XSync() after the XBell() so that actually gets sent to the
AC server and not just buffered, then immediately discarded on program exit.
Oh. Of course. Stupid. Thanks.
That works. I guess the other clients must call
Two functions in the DMX glxproxy code loop over all the backend
screens, starting at the highest numbered and counting down to
the lowest.
Previously, for each screen, the code would allocate a buffer
large enough to read the reply from the backend, copy that reply
into the buffer, and then if
I guess the other clients must call XBell() with percent=0?
Probably. The way the percent argument (which is only sort-of a
percentage; it runs from -100 to 100) is interpreted makes it
reasonably clear to me that the intent is that 0 be some sort of
nominal user-set volume, with programs able
Peter Hutterer peter.hutte...@who-t.net writes:
Chris Clayton (1):
kdrive: fix build error on gcc 4.8 for out-of-bounds array access
Thomas Klausner (2):
Fix bug in cursor handling.
Fix typo in configure warning.
94d4e29..6f89ae3 master - master
--
