On 17/12/2015 4:09 AM, Alexander Surkov wrote:
Don't we need an extra aMaxRanges argument? It seems any other
array-related method has it.
The older methods (e.g. IAccessible2::relations) used client allocated
arrays, but this makes life a bit difficult. These did need a max
argument. The newer methods (e.g.
IAccessibleTableCell::columnHeaderCells) are server allocated arrays
which the client frees with CoTaskMemFree. These do not need a max
argument. However, we *should* document that the parameter is a server
allocated array and needs to be freed with CoTaskMemFree, just as we do
for IAccessibleTableCell::columnHeaderCells.
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
