With the big movements that happened in mmsystem.h I noticed that
mixerMessage16 returns a UINT16.
But I thought that all the xxxMessage16 APIs were supposed to return
a DWORD. Or is this an exception?
--
Francois Gouget [EMAIL PROTECTED]http://fgouget.free.fr/
Francois Gouget wrote:
With the big movements that happened in mmsystem.h I noticed that
mixerMessage16 returns a UINT16.
But I thought that all the xxxMessage16 APIs were supposed to return
a DWORD. Or is this an exception?
yup... mixerMessage16 is wrong (but it was already wrong
On Wed, 27 Sep 2000, Eric Pouech wrote:
Francois Gouget wrote:
With the big movements that happened in mmsystem.h I noticed that
mixerMessage16 returns a UINT16.
But I thought that all the xxxMessage16 APIs were supposed to return
a DWORD. Or is this an exception?
yup...
Hi,
I noticed that many functions in mmsystem.[ch] use UINT/UINT16 as
their return type rather than the official MMRESULT/MMRESULT16,
MCIDEVICEID/MCIDEVICEID16 or MCIERROR/MCIERROR16. So I started a patch
to make things closer to the specs.
But I found that some 16 bit functions
Francois Gouget wrote:
Hi,
I noticed that many functions in mmsystem.[ch] use UINT/UINT16 as
their return type rather than the official MMRESULT/MMRESULT16,
MCIDEVICEID/MCIDEVICEID16 or MCIERROR/MCIERROR16. So I started a patch
to make things closer to the specs.
But I found