[Python-bugs-list] [ python-Bugs-735674 ] libwinsound.tex is missing MessageBeep() description

[SourceForge.net]

Bugs item #735674, was opened at 2003-05-10 07:44
Message generated for change (Comment added) made by tim_one
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=735674&group_id=5470

Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Walter Dörwald (doerwalter)
Assigned to: Guido van Rossum (gvanrossum)
Summary: libwinsound.tex is missing MessageBeep() description

Initial Comment:
libwinsound.tex is missing a description of the 
MessageBeep() function.

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2003-05-11 19:03

Message:
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.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2003-05-11 16:40

Message:
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).

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2003-05-11 12:03

Message:
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.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2003-05-11 06:21

Message:
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.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2003-05-11 00:52

Message:
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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=735674&group_id=5470