This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: libwinsound.tex is missing MessageBeep() description
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gvanrossum Nosy List: doerwalter, gvanrossum, tim.peters
Priority: normal Keywords:

Created on 2003-05-10 11:44 by doerwalter, last changed 2022-04-10 16:08 by admin. This issue is now closed.

Messages (8)
msg15959 - (view) Author: Walter Dörwald (doerwalter) * (Python committer) Date: 2003-05-10 11:44
libwinsound.tex is missing a description of the 
MessageBeep() function.
msg15960 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2003-05-11 04:52
Logged In: YES 
user_id=31435

Assigned to Guido because, IIRC, he added this function.
Guido, why did you add it?  It seems like a redundant way 
of calling winsound.PlaySound() with the SND_ALIAS 
argument.
msg15961 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-05-11 10:21
Logged In: YES 
user_id=6380

I added it because I discovered that on my Win98 machine
certain calls to MessageBeep() make a funny sound (a very
brief distorted click) rather than what they are supposed to
do. I haven't found docs showing the resource names used by
MessageBeep() that I could pass to SND_ALIAS.
msg15962 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2003-05-11 16:03
Logged In: YES 
user_id=31435

I don't think you meant what you wrote -- that you added 
MessageBeep() because MessageBeep() doesn't do what 
it's supposed to do.  If PlaySound() gave a distorted click, 
and you're using it right, then you probably have a 
corrupt .wav file associated with the sound you tried to 
play; you can check that more directly via the Sounds 
applet in Control Panel (which lists the .wav file associated 
with sound names, and has a preview button to play them 
directly).

About docs, did you read the Python docs for PlaySound
()?  For example,

MessageBeep(MB_ICONASTERISK)

should do the same as

PlaySound('SystemAsterisk', SND_ALIAS)

The docs don't directly list MB_XYZ equivalents, but 
they're easy to guess from the Python docs.
msg15963 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-05-11 20:40
Logged In: YES 
user_id=6380

I really did mean what I wrote -- I wanted to experiment
with different calls to MessageBeep() to see how far the
damage extends.

I tried the control panel and none of the sounds there are
broken -- yet MessageBeep() is broken.

We can look at this tomorrow in the office (my laptop is
turned off right now and I have no time for experiments).
msg15964 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2003-05-11 23:03
Logged In: YES 
user_id=31435

Hmm.  OK.  There's a disconnect here somewhere.  Like 
why would you add a function to Python when you don't 
think it works correctly?  I understand wanting to 
experiment on your own box.  If it doesn't work, though, 
why add it to the distribution?

FWIW, the 5 MB_xyz thingies work OK with MessageBeep
() on my Win98SE laptop.
msg15965 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2003-05-11 23:57
Logged In: YES 
user_id=31435

FYI, the MB_xyz thingies work OK with MessageBeep
() on my Win98SE desktop too.
msg15966 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2003-05-16 01:42
Logged In: YES 
user_id=6380

LaTeX docs checked in. Case closed.
History
Date User Action Args
2022-04-10 16:08:41adminsetgithub: 38482
2003-05-10 11:44:10doerwaltercreate