[PATCH 2/2] winmm: MCI_BREAK_HWND handling now matches Wine's 1999 MCI_DefYieldProc.

Joerg-Cyril.Hoehle at t-systems.com Joerg-Cyril.Hoehle at t-systems.com
Wed Feb 27 08:10:06 CST 2013


the other patch is 2 years old, but it's only now that I looked closer at MCI_DefDriverProc
and noticed the DWORD = WORD(key) + WORD(16 bit window handle) splitting there.

My tests could not verify that splitting via the MCI_BREAK_HWND command,
yet here's a patch to match Wine's MCI_DefDriverProc expectations.
(perhaps I should test using mciavi instead of mcimidi?)

Giving that DefYieldProc is from 1999, perhaps that was w3.1 behaviour?

It would be good if somebody with knowledge of user.dll windows messaging
would look at and implement the MCI yield stuff (see mciDriverYield and mciSetYieldProc).

 Jörg Höhle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-winmm-MCI_BREAK_HWND-handling-now-matches-Wine-s-19.patch
Type: application/octet-stream
Size: 1238 bytes
Desc: 0002-winmm-MCI_BREAK_HWND-handling-now-matches-Wine-s-19.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20130227/4967671f/attachment.obj>

More information about the wine-patches mailing list