IEnumExplorerCommand.Next array marshaling SizeParameterIndex incorrect?
See original GitHub issueHere, should the celt
be used as the size parameter, instead of pceltFetched
?
That is should the SizeParamIndex
be set to 0, instead of 2?
The documentation says :
celt
Specifies the number of elements to fetch.pceltFetched
When this method returns, contains a pointer to the number of elements actually retrieved.
When this method gets called, the out parameter pceltFetched
will always be the default value zero,
so, seems pUICommand
should be initialized as an array of size celt
, instead of pceltFetched
?
otherwise, the initial value of pUICommand
will always be an empty array and can’t be populated later.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
IEnumExplorerCommand::Next method (shobjidl_core.h)
Retrieves a specified number of elements that directly follow the current element.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you. That helps my understanding immensely. I think I need to expand my testing to including implementations and then adjust all the
SizeParamIndex
values accordingly.I have updated all interfaces with similar patterns to using the input size parameter for SizeParamIndex.