- 13 Jan, 2014 13 commits
-
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
Also lock/unlock the module only on creation/destruction of the object.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Nikolay Sivov authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Dmitry Timoshkov authored
-
- 10 Jan, 2014 27 commits
-
-
Hans Leidekker authored
-
Hans Leidekker authored
-
Jacek Caban authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
A surface can stay in DIB or user memory just fine. When buffers get their own location an exception for them has to be added.
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
-
Stefan Dösinger authored
Buffers, heap memory, user memory and DIBs will have their own locations. This field specifies which location is used when the surface is mapped.
-
Jacek Caban authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Dmitry Timoshkov authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Michael Stefaniuc authored
include: There is no need to duplicate CLSID_DirectMusicAudioPathConfig as CLSID_DirectMusicAudioPath. CLSID_DirectMusicAudioPath is private to Wine and produces the confusion between the COM objects DirectMusicAudioPath and DirectMusicAudioPathConfig. But those are totally different things.
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-