Implement Windows GDI renderer backend.#9406
Open
MouriNaruto wants to merge 1 commit into
Open
Conversation
|
卧槽，爷爷，你关注的up主复活发布新作品了 |
|
居然还有后续 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
First, here is the screenshot for the Windows GDI renderer backend example running under both normal Windows SKU and Windows PE.
Note
This PR is the continuation of #2724.
After about 6 years, I have finally implemented the fast-path based on the Windows GDI API and rewrited the software triangle renderer part. The performance should be relatively much better.
Kenji Mouri