On Fri, 2010-07-09 at 11:31 +0200, Stefan Dösinger wrote: > Am 09.07.2010 um 03:21 schrieb Misha Koshelev: > > wined3d: Add WINED3DUSAGE_OVERLAY. > This was added for overlay surfaces that only exist in ddraw. The mask is to > make sure d3d9 apps don't accidentally pass this flag to wined3d. I don't > think a test is needed, unless we find a windows app that tries to use this > flag and expects a certain outcome. > > d3d9 gained support for overlay surfaces in windows 7, so maybe we can > migrate wined3d's overlay support to use the d3d9 way and adjust ddraw.dll to > use it. >
Thanks. I will have to process this. But just to clarify: 1) I am actually testing something else (index buffer description in mesh object): See my patch here please http://github.com/misha680/wine/commit/d182054430ea4976744b49d3d74f1f04039ffa6f Just to be thorough I am testing usage flag as well and that is why I noticed the discrepancy. The patch that implements is here: http://github.com/misha680/wine/commit/519f38e9996892f7be47b5fc2332c3a807df4aeb You can see that the usage is still a todo_wine. I will leave it like this, but if you think there's a better way please let me know. > > d3d9 gained support for overlay surfaces in windows 7, so maybe we can > migrate wined3d's overlay support to use the d3d9 way and adjust ddraw.dll to > use it. > 2) I am going to have to re-read this later to understand it, but I will keep this on a back-burner as something perhaps to do after: http://bugs.winehq.org/show_bug.cgi?id=22918 Misha p.s. I have updated my Wiki page to reflect my current direction http://wiki.winehq.org/MishaKoshelev I am sorry I've completely gone anti-general format - instead of one TODO list I have three (CURRENT = _will do_, FUTURE??? = ideas that may or may not do, PAST = already done). If this is really a big problem I will change back but I like doing one thing at a time while having potential future ideas to work on (thanks Dan and Stefan, well and everyone else).
