[DXGI] KeyedMutex.Acquire - cannot check for WAIT_ABANDONED and WAIT_TIMEOUT #103

ArtiomCiumac · 2013-07-09T19:52:55Z

The issue discussion is started on the forum:
http://www.sharpdx.org/forum/5-api-usage/3337-dxgi-keyedmutex-acquire-cannot-check-for-wait-abandoned-and-wait-timeout

In current implementation it is not possible to check for WAIT_ABANDONED and WAIT_TIMEOUT results as specified in documentation:
http://msdn.microsoft.com/en-us/library/windows/desktop/ff471339%28v=vs.85%29.aspx

…itAbandoned and Result.WaitTimout. Add ResultDescriptor for common errors. Improve SharpGen to support return and check of HRESULT at the same time.

xoofx · 2013-07-27T11:48:38Z

Fixed by commit b1596dd

…sult.WaitAbandoned and Result.WaitTimout. Add ResultDescriptor for common errors. Improve SharpGen to support return and check of HRESULT at the same time.

ghost assigned ArtiomCiumac Jul 9, 2013

xoofx added a commit that referenced this issue Jul 27, 2013

[DXGI] Fix issue #103. KeyedSync.Acquire return Result. Add Result.Wa…

b1596dd

…itAbandoned and Result.WaitTimout. Add ResultDescriptor for common errors. Improve SharpGen to support return and check of HRESULT at the same time.

xoofx closed this as completed Jul 27, 2013

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[DXGI] KeyedMutex.Acquire - cannot check for WAIT_ABANDONED and WAIT_TIMEOUT #103

[DXGI] KeyedMutex.Acquire - cannot check for WAIT_ABANDONED and WAIT_TIMEOUT #103

ArtiomCiumac commented Jul 9, 2013

xoofx commented Jul 27, 2013

[DXGI] KeyedMutex.Acquire - cannot check for WAIT_ABANDONED and WAIT_TIMEOUT #103

[DXGI] KeyedMutex.Acquire - cannot check for WAIT_ABANDONED and WAIT_TIMEOUT #103

Comments

ArtiomCiumac commented Jul 9, 2013

xoofx commented Jul 27, 2013