GNU bug report logs - #1305
All code that currently beeps should use visual bell instead

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: alan <at> idiocy.org, 1305 <at> debbugs.gnu.org, mwd <at> md5i.com, stefan <at> marxist.se, jasonspiro4 <at> gmail.com, monnier <at> iro.umontreal.ca, dgutov <at> yandex.ru, larsi <at> gnus.org
Subject: bug#1305: All code that currently beeps should use visual bell instead
Date: Fri, 30 Apr 2021 11:03:51 +0300

> Date: Fri, 30 Apr 2021 07:27:25 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: dgutov <at> yandex.ru, alan <at> idiocy.org, 1305 <at> debbugs.gnu.org, mwd <at> md5i.com, 
>     stefan <at> marxist.se, jasonspiro4 <at> gmail.com, monnier <at> iro.umontreal.ca, 
>     larsi <at> gnus.org
> 
> "Flashing a window means changing the appearance of its caption bar as if 
> the window were changing from inactive to active status, or vice versa. 
> [...] Typically, a window is flashed to inform the user that the window 
> requires attention but that it does not currently have the keyboard 
> focus." [1]
> 
> [1] https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-flashwindow
> 
> But even that doesn't describe the effect accurately, the feeling I have 
> is closer to "the frame briefly vibrates".  As I said, I use Windows only 
> rarely, so my feeling is perhaps not right.

What I see is exactly what the MS documentation describes: the frame's
title bar blinks (a.k.a. "flickers"), which is very hard to notice;
and the corresponding tab on the task bar flashes, which is much more
prominent.  IME, this happens in all Windows versions.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.