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

Previous Next

Full log

Message #811 received at 1305 <at> debbugs.gnu.org (full text, mbox):

From: Gregory Heytings <gregory <at> heytings.org>
To: Eli Zaretskii <eliz <at> gnu.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: Re: bug#1305: All code that currently beeps should use visual bell
 instead
Date: Fri, 30 Apr 2021 07:27:25 +0000

>> Yes, "flash" is perhaps not the best word here, perhaps "vibrate" is 
>> better.
>
> That word still doesn't tell me what you think happens.  Can you 
> describe in more detail what exactly you see, and on which version of 
> MS-Windows?
>

Windows 10.

I don't know how to describe this better than with the words "flash" or 
"vibrate", so I looked at the docs:

"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.

Previous Next

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