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.
ProEssentials' WebForm .NET Chart Controls purely serve content in the form of images or ActiveX states. The WebForms do not render .NET dependent WinForm controls within the Browser. No dependency on the Framework, version of Framework, or version of Internet Explorer is thus required for client systems/browsers. Also, even though the WebForm controls do render ActiveX states to the client, no COM dependency is required on the server and no COM functionality needs to be registered on the server.
Any interactive-charting capabilities is only provided by rendering ActiveX controls to the browser. Thus, embedding client-side script within your ASPX page will be required to provide interactive logic. As part of the ASPX page processing, your script will be passed to the client and execute client-side as needed. See the ASP.NET Walk-throughs within Chapter 2 and the PE8WebDemo example project for detailed how-to info.
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 as ActiveX and client-side script technology is used for handling events client-side.
©2018 Gigasoft, Inc. | All rights reserved.
Gigasoft is a registered trademark, and ProEssentials a trademark of Gigasoft, Inc.