Desktop Duplication API returns unreliable pointer info in Win10 version 2004
Hi there,
I'm using the Desktop Duplication API for capturing pointer updates (i.e. pointer shape changes or changes between software and hardware cursor modes).
The pointer info being returned under FrameInfo in AcquireNextFrame() was reflective of the cursor changes happening on the actual desktop when I was on Win10 version 1909. After updating to version 2004, this doesn't seem to be the case, as it doesn't capture changes from hardware > software mode (via PointerPosition.Visible), and doesn't always detect changes to the shape either (via PointerShapeBufferSize being > 0). There's been a case where this issue was also seen with the latest Windows updates to 1909.
Does anyone have any input / insight into this issue? Is there ongoing support for the Desktop Duplication API in the latest Windows versions?
Thanks.