Conversation
We need to redo the initialization because WinDrawLib interface modules do not match 1:1 to the implementation modules, from now on. In particular, with the D2D1 back-end, we use DWrite both for the string API and (new not yet implemented) advanced text API. The reason for disntinguishing string and text API is that later, we shall likely implement the text API also for GDI+ back-end using Uniscribe, but the simple string API does not need to load it.
The cached canvas retains the painted contents; so we can skip all the painting (as long as we need to paint the stuff dfferently).
Note it is really supported only in DWrite backend on Windows 8 and newer. If not supported, it falls back to left alignement.
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
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.
Disclaimer: This is work in progress. Anything here can be changed anytime. You have been warned.
WinDrawLib already supports simple string rendering. This PR is about more advanced text rendering, so things like this could be implemented on top of it:
Note all this is for D2D1 + DWrite back-end only. Once we have something reasonably complete, we might consider also adding support for gdi+ back-end.
Rendering features:
Additional features:
IDWriteTextLayout::GetOverhangMetrics())IDWriteTextLayout::GetLineMetrics())IDWriteTextLayout::GetClusterMetrics())