Unify the Private Data docs between D3D9-D3D12 #1976
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Uses D3D12 wording as a template as it was the most exhaustive.
|
@CookiePLMonster : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
stevewhims
approved these changes
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uses D3D12 wording as a template as it was the most exhaustive. With these changes, private data should consistently document the
IUnknown-type data that was previously lacking.This repository contains D3D7 docs, but D3D8 docs seem to be archived and un-editable? They would need the changes from D3D9 mirrored.