-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DirectWrite: Many classes have not been tagged with the right version #3984
Comments
Thank you for opening an issue! One of our team members will get back to you with additional information. If this is a product issue, please close this issue and contact the product's support instead. For a list of support websites, see Support for Microsoft products and apps. |
@drewbatgit Can you take a look? |
This type of documentation error makes it really hard to use newer functionality of DirectWrite, and to trust this metadata in general. You never really know what version of Windows you need for any particular interface and thus have to stick with an older common denominator, e.g. the original From my own investigation into this from a few years ago I know that everything up to |
I found a new error. It is wrote that IDWriteFontCollection1 have been introduced in Windows 7, Windows Vista with SP2 and Platform Update for Windows Vista, but I am pretty sure it has been introduced in the first release of windows 10 |
That's probably true since it's part of |
All these enumerations, classes and structures are tagged has
Minimum supported client : Windows 10 Build 20348
But in reality, they have been introduced in another version.
Windows 10 Build 16299
(Source of this information)Windows 10 Build 17134
(Source of this information)Windows 10 Build 17763
(Source of this information)The text was updated successfully, but these errors were encountered: