- 10 Jan, 2014 40 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
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Michael Stefaniuc authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Ken Thomases authored
winemac: For ChangeDisplaySettingsEx(), if caller didn't specify, prefer non-interlaced and unstretched modes.
-
Ken Thomases authored
When originalDisplayModes has entries, the app is active. When the app is active, latentDisplayModes is empty.
-
Ken Thomases authored
-
Ken Thomases authored
We only care if we have changed the mode and we're changing it back to its original. Even if the current mode matches the target mode, we may still need to release the displays and clear the entry from originalDisplayModes.
-
Ken Thomases authored
winemac: Don't assume the current display mode is the original if we don't have the displays captured. Another process may have changed the display mode before we queried the current mode, so we may be seeing a non-original mode.
-