|
New development? Start with WinUI. WinUI 3 is Microsoft's current-generation Windows UI platform and the modern successor to WPF, whose visual layer remains tied to the now-ancient DirectX 9. Our WinUI interface renders through Direct3D and Direct2D composition swap chains hosted directly in the XAML visual tree, targets .NET 10, and carries the new built-in menu and dialog UX. WPF and Winforms remain fully supported and are the right choice for an existing application - but for new work, WinUI is where we recommend you begin. See New V11 Features for the full WinUI story.
Gigasoft.ProEssentialsWinUIProEssentials' WinUI 3 chart controls target .NET 10 and the Windows App SDK. They expose the same PExxx properties, methods, and events as the Winform, WPF and WebForm controls, so the links below lead to the same combined reference content. In XAML, reference the namespace with xmlns:pe="using:Gigasoft.ProEssentials".
WinUI Specific Properties The WinUI interface adds a few properties of its own. RenderPriority controls how the control schedules its Direct3D / Direct2D render work, with values Auto, Low, Normal and High; Auto (the default) keeps the interface responsive during interaction while protecting modal dialogs from render starvation. UseWinUIUX enables the new built-in menu and dialog user experience; it is true by default, set it false to fall back to the legacy Win32 popup menu and dialogs. PeAnnotation.EnableWinUIDrawTable opts the control into a dedicated composition layer for real-time table annotations (PEdrawtable). See New V11 Features for a fuller description.
Winform, WPF, and WinUI assemblies ship as architecture-specific x64 and ARM64 flavors (plus x86 on .NET Framework 4.8) and as a self-contained AnyCpu flavor on .NET Framework 4.8, .NET 8, and .NET 10 (the WinUI interface is .NET 10 only), and all are available as NuGet packages. See .NET Deployment for what to distribute with each.
WPF vs WinForm Development The WPF interfaces have a WPF specific property RenderSizeXdpi.This controls if a non-96 dpi system compensates for dpi by multiplying RenderSize by dpi factor. True by default, font sizes and line thicknesses will not scale on non-96dpi systems. Instead, image sharpness is maintained rather than allowing lines and text to become fuzzy. You may prefer to change this setting to False if you prefer the chart to become fuzzy if the system has larger than normal fonts, possibly to match other fuzzy graphics within the app.
Gigasoft.ProEssentialsWebProEssentials' WebForm .NET Chart Controls purely serve content in the form of images or binary chart states.
The links below link to combined WinForm / WebForm content as the WebForm's properties and methods are similar to the WinForm's properties and method. However, all the WinForm events (such as PeCursorMoved, PeDataHotSpot) are not present within the WebForm interfaces.
Gigasoft.ProEssentials.Enums Members
|
|
©2026 Gigasoft, Inc. | All rights reserved.
Gigasoft is a registered trademark, and ProEssentials a trademark of Gigasoft, Inc. |
|