Extend gettextureinfo to read arbitrary arrays and output their size … #1444
+192
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch ties in with an OIIO patch: Add get_texture_info_type to query TypeDesc...
It extends the gettextureinfo call with an extra int output parameter, output int param_array_len;
If the basetype of destination equals the basetype of the data under paramname, and the array length of destination is large enough to fit the data, it will store the data in destination and the array length of the data in param_array_len. This allows us
to be more flexible when working with arrays stored in texture metadata.
Shader example: