SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
SciChart is a cross-platform WPF & Silverlight component, which shares around 95% of its codebase between the two platforms. I’m sure you’re aware there are a few deficiencies in the Silverlight platform, for instance, there is no System.Diagnostics.StopWatch, no ICloneable interface, no UIElement.SnapsToPixels etc!
Where you see classes like this it is to provide a syntactically correct equivalent for a WPF class or method which doesn’t exist in Silverlight. To give us the best cross-platform compatibility, the namespaces are the same as in WPF. It’s a technique many bloggers & tech writers use to create cross-platform code.
SciChart also uses WriteableBitmapEx, which is an open source 2D drawing engine, licensed under MS-PL. We try not to deviate too much from their source, which uses the namespace System.Media.Imaging so that WriteableBitmap extension methods are available wherever you reference a WriteableBitmap.
To ensure your code doesn’t get polluted with ours in dummy namespaces, those classes are marked as internal. May I ask, is there a problem with conflicting namespace on a class from SciChart with a MS namespace? If so, let me know which, I can rectify this by ensuring it is marked as internal.
Please login first to submit.