From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: 74863@debbugs.gnu.org
Subject: bug#74863: 31.0.50; Problems with play-sound on MS-Windows
Date: Sun, 15 Dec 2024 20:48:59 +0200 [thread overview]
Message-ID: <86a5cwrdd0.fsf@gnu.org> (raw)
In-Reply-To: <b6148976-6c70-41d8-9a6a-0d4e7bf8226c@imayhem.com> (message from Cecilio Pardo on Sun, 15 Dec 2024 19:33:35 +0100)
> Date: Sun, 15 Dec 2024 19:33:35 +0100
> Cc: 74863@debbugs.gnu.org
> From: Cecilio Pardo <cpardo@imayhem.com>
>
> >> + if (in_memory)
> >> + i_result = !PlaySound (psz_file_or_data, NULL, SND_MEMORY);
> >
> > AFAIU, the documentation seems to say that the string passed as the
> > first argument to PlaySound is limited to 256 characters (i.e. bytes)?
> > If so, how do we play longer sounds?
>
> I think this limitation applies only when the argument points to a
> string, and not when using SND_MEMORY, which is documented with: "The
> pszSound parameter points to a sound loaded in memory."
>
> It's true the documentation doesn't say so, and I haven't found any
> clarification by Microsoft, but SND_MEMORY would be useless otherwise.
> Also I see normal usage searching the internet.
So there are no limitations whatsoever on the length of that string?
next prev parent reply other threads:[~2024-12-15 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 23:50 bug#74863: 31.0.50; Problems with play-sound on MS-Windows Cecilio Pardo
2024-12-14 8:42 ` Eli Zaretskii
2024-12-14 14:07 ` Cecilio Pardo
2024-12-14 14:56 ` Eli Zaretskii
2024-12-15 1:35 ` Stefan Kangas
2024-12-15 20:36 ` Cecilio Pardo
2024-12-15 22:16 ` Stefan Kangas
2024-12-15 11:55 ` Cecilio Pardo
2024-12-15 12:50 ` Eli Zaretskii
2024-12-15 18:33 ` Cecilio Pardo
2024-12-15 18:48 ` Eli Zaretskii [this message]
2024-12-15 20:38 ` Cecilio Pardo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5cwrdd0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74863@debbugs.gnu.org \
--cc=cpardo@imayhem.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).