Win2D 1.17.0 – bugfixes and stable APIs


Win2D version 1.17.0 is now available on NuGet (for Windows 10 or Windows / Phone 8.1) and GitHub.

This release fixes a couple of bugs that were reported by customers on github.

It also removes the “experimental” warning tag from a final set of APIs that we now consider to be stable:

  • HDR color support
    • *Hdr properties matching all existing Color properties
    • CanvasSolidColorBrush constructor overload
    • CanvasGradientStopHdr
    • Clear overload
  • ColorManagementEffect
  • ColorManagementProfile
  • ColorManagementEffectQuality
  • ColorManagementRenderingIntent
  • TableTransfer3DEffect
  • EffectTransferTable3D
  • CanvasTextFormat
    • CustomTrimmingSign
    • TrimmingSign
  • CanvasTextLayout
    • CustomTrimmingSign
    • DrawToTextRenderer
    • GetCustomBrush
    • GetTypography
    • SetCustomBrush
    • SetInlineObject
    • SetTypography
    • TrimmingSign
  • CanvasAnalyzedBidi
  • CanvasAnalyzedBreakpoint
  • CanvasAnalyzedGlyphOrientation
  • CanvasAnalyzedScript
  • CanvasCharacterRange
  • CanvasFontFace
  • CanvasFontFileFormatType
  • CanvasFontInformation
  • CanvasFontProperty
  • CanvasFontPropertyIdentifier
  • CanvasFontSet
  • CanvasFontSimulations
  • CanvasGlyph
  • CanvasGlyphJustification
  • CanvasGlyphMetrics
  • CanvasGlyphOrientation
  • CanvasGlyphShaping
  • CanvasJustificationOpportunity
  • CanvasLineBreakCondition
  • CanvasNumberSubstitution
  • CanvasNumberSubstitutionMethod
  • CanvasScaledFont
  • CanvasScriptProperties
  • CanvasScriptShape
  • CanvasTextAnalyzer
  • CanvasTextGridFit
  • CanvasTextMeasuringMode
  • CanvasTextRenderingMode
  • CanvasTextRenderingParameters
  • CanvasTrimmingSign
  • CanvasTypography
  • CanvasTypographyFeature
  • CanvasTypographyFeatureName
  • CanvasUnicodeRange
  • ICanvasTextAnalyzerOptions
  • ICanvasTextInlineObject
  • ICanvasTextRenderer
  • CreateGlyphRun
  • TextRenderingParameters

 


Comments (1)

  1. Chris says:

    Are there any plans to write a blog post that elucidates what the internal Microsoft people are thinking re: graphics APIs post-Xamarin acquisition? I know Xamarin has the set of cross-platform graphics APIs they expose while allowing people to still use the platform specific APIs directly if they want.

    I assume many Windows APIs contain some optimizations which might work cross-platform if they get compiled into the apps to make Xamarin an even more competitive offering as a cross-platform path.

    I will look into Xamarin again in a couple years after the dust settles a bit, but I’m just curious what’s brewing in these areas at MS.

    Thanks.

Skip to main content