- 20 Nov, 2013 8 commits
-
-
Henri Verbeet authored
-
Francois Gouget authored
-
Francois Gouget authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Frédéric Delanoy authored
-
Vincent Povirk authored
-
Vincent Povirk authored
-
- 19 Nov, 2013 22 commits
-
-
Detlef Riekenberg authored
-
Akira Nakagawa authored
-
Sebastian Lackner authored
-
Michael Müller authored
-
Nikolay Sivov authored
-
Nikolay Sivov 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
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Andrew Eikum authored
-
- 18 Nov, 2013 10 commits
-
-
Vitaly Lipatov authored
-
Frédéric Delanoy authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
André Hentschel authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
Calling wined3d_surface_set_mem() might cause the surface container to be accessed, for example when invalidating resource locations. This would become a problem once we assume surfaces always have a container, and is pointless anyway because the surface is being destroyed.
-