Pass 0 instead of None to VBuf_getControlFieldNodeWithIdentifier (#19365)
Closes ##19258
fixes #18879
Summary of the issue:
There is a type incompatibility between some return values from virtualBuffers.VirtualBuffer.getIdentifierFromNVDAObject (which seemingly returns None some of the time), and NVDAHelper.localLib.VBuf_getControlFieldNodeWithIdentifier, which expects its 2nd and 3rd arguments to be integers.
Description of user facing changes:
This seems to be intermittent and only to produce excessive log output.
Description of developer facing changes:
None
Description of development approach:
When passing docHandle and objId to VBuf_getControlFieldNodeWithIdentifier, pass 0 instead of None. Note that before the 64-bit transition, this FFI binding had no typing information, so ctypes would have converted None to 0 silently.