We are really excited to announce, that SciChart iOS/ Android / Xamarin v2.2 is released!
What’s New in SciChart iOS /Android /Xamarin v 2.2?
There is a large number of improvements and bug fixes made in SciChart iOS/ Android / Xamarin v2.2. We have made a major step forward by refactoring of our examples, fixing memory leaks, crashes, and bugs and other improvements. It is recommended for all users of SciChart v2.1 to update to the latest version! Please see more information below:
- iOS Charts have been made compatible with Xcode 10 and iOS 12 by removing deprecated libstdc++ with libc++. SciChart iOS v2.2 no longer uses this library and will work with future version(s) of iOS & Xcode.
- Android Charts showcase demo and examples project has been updated to work with Android Studio 3.1: updated to Gradle 4.4; updated to SDK 27 ( Oreo ).
- Android library has been updated to support library 27.1.0 and Kotlin 1.2.30
- Fixed hitTestAxis method which caused issues with axis tooltips values
- SCIOS-626: fixed annotations don’t clip by axes and drawn over them.
- SCIOS-639: fixed annotation added after chart initializing is not being rendered
- SCIOS-640: fixed Incorrect casting from Swift.Array<Double> to SCIGeneric
- SC-DROID-526: fixed incorrect rendering of RTL text caused by trying to reuse text layout ( it was defined it with Integer.MAX_VALUE width )
- SC-DROID-525: fixed incorrect text rendering in heatmap ( added flipping of x and y coordinates if the chart is vertical )
- SCIOS-624: fixed placing annotations below chart doesn’t work
- SC-DROID-521: fixed incorrect work of sweep animation with PaletteProvided which was caused by adding new points into render pass data
- SC-DROID-522: refactored PieSegment and PieDonutRenderableSeriesBase to correctly handle case when PieSegment changes;
- SC-DROID-520: fixed incorrect hit test which is caused by updating xValues and yValues but not indices:
- now render pass data remains the same and we just draw spline lines and perform hit test on original data;
- updated spline calculations which resulted in all NaN values – added n parameter to prevent going outside renderPassData bounds if x/yValues array are larger than
- actual renderPassData size; removed unused code from spline calculations;
- changed SplineLineRenderableSeries: now we calculate spline coords for coordinates instead of values right before drawing for correct work of animations;
- Added behavior options for tooltip modifiers; and added bindings.
- Fixed: issue in legendDataSource.
- Fixed: crash during measuring custom legend item is using a custom nib file from the main bundle.
- Fixed: addPointsPerformance demo example
- Fixed: crash when try using custom legend item nib file from the main bundle.
- Fixed: getter for color in gradient brushes.
- SC-DROID-518: fixed incorrect rendering of rects when use RenderSurface – it was caused by incorrect points index
- Fixed: memory leak in renderableSeries base
- Fixed broken units tests: removed usage of reflection for getting parameter names and replaced it on Mono.Cecil which allows doing the same but without loading dependencies of assembly;
- SC-DROID-511: Fixed cursor tooltip which wasn’t shown for the second half of the last candle in series; changed calculations in HitTestHelpers.isPointWithinXBounds() to prevent precision problems when performing hit test
- SC-DROID-513: fixed incorrect layout of horizontal legend – added usage of HorizontalScrollView when legend has horizontal orientation
- Fixed warning: atomic property cannot pair a synthesized setter/getter with a user-defined setter/getter
- Fixed: color of marker view of legend item
- Fixed: broken test by using a proper calendar in SCIDateUtil instead or using NSCalendar currentCalendar
- Fixed: flickering of the edge labels (also hiding them sometimes)
- Fixed: error when sometimes onVisibleRangeChanged() wasn’t called at the end of animation; added setMinMaxForced into IRange to set new Min/Max values even if they are equal to current Min/Max values + added tests
- Fixed: non-working onVisibleRangeChange method in IViewportManager; modified unit tests;
- Fixed: incorrect buildToolsVersion and updated SciChart dependencies to v2.1 in exported projects
- Fixed: broken parameter names generation in Xamarin: updated path required for metadata generator;
- SC-DROID-509: fixed incorrect drawing of pie and donut charts when there is only one segment; refactored drawing code;
- SCIOS-622: fixed hitTest doesn’t work properly with categoryDateAxis
- Fixed: SCIChartHeatmapColourMap while creating from xib
- SC-DROID-503: fixed rounding error when formatting label in LabelProvider for the category axis
- Added: main.storyboard and launchScreen back to the project
- SCIOS-623: refactoring swift examples:
- refactored speedTesting, hitTest, zoomandPan groups;
- refactored: styling and theaming group, axis behaviour group, ECG chart, oscilloscope chart, realtime ticking stock chart, stock chart example, multipane stock chart example, realtime chart examples, multi-series chart examples, gauge chart examples, pie and donut series, using themeManager example, and custom charts examples;
- added common Init method to ExampleViewBase which supposed to contain commonViewINItialisation;
- added labelProvider to columns side-by-side examples;
- SCIOS-625: legend changes:
- updated Xamarin.iOS bindings and examples;
- added property which allows dequeuing custom legend items from UICollectionView;
- refactored updated\changed methods in dataSource;
- added handling of legendPosition
- Removed duplicate declaration in h file (already defined in protocol). Also named file properly
- Added attach To and detach methods to SCIPieSegment
- Added handling of showCheckBoxes and seriesMarkers
- Added: SCIChartLegendHorizontalLayout which allows the legend to wrap it’s content horizontally.
- Added: SCIChartLegendVerticalLayout which allows legend to wrap it’s content; Removed redundant code
- Added: ctors to h file
- Added missing ctors for SCISeriesInfo inheritors
- SC-DROID-510: added correct handling of tooltip placement when a chart is rotated; changed SliceLayout to prevent overlapping of rollover tooltips
- Added maxAsDouble and minAsDouble to omit conversion calls to SCIGeneric and SCIGenericDouble, even when use asDoubleRange; made asDoubleRange deprecated;
- Updated swift demo app labelProviders according to recent changes, reverted accidentally commented out deprecated properties in tooltip modifier styles
- Added: inMinMaxValid method into ranges
- Added: themeId to SCIThemeColorProvider
- Made SCIRenderableSeriesProtocol conform to SCIInvalidatableElementProtocol
- Changed: SeriesInfo seriesColor is now of type UIColor and isn’t nil every time
- Refactored: default ViewportManager to handle AutoRange.Always case in tryPerformAutoRange instead of onUpdateAxis; updated tests;
- SC-DROID-480: Added ClipModeTarget which allows specifying target range which will be used for clipping in ZoomPanModifier and XAxisDragModifier; fixing typo in name of setClipModeX method in modifier builders;
- SC-DROID-505: added correct disposing of resources for OpenGL based RenderSurface implementations; removed onSurfaceDestroyed method because it wasn’t actually called anywhere
- Changed: default values for pie\donut charts – drawLabels and spacing
- Reworked speedTest examples as well as modifyAxisBehaviour ones.
- Moved missing ctors to SCIArrayController from SCIArrayControllerProtocol
- Created view from xib files
- SC-DROID-506: added usage of Path instead of simple drawLine to provide correct handling of dashed lines in modifiers.
Where to get iOS / Android / Xamarin v2.2?
You can get the SciChart iOS/Android/ Xamarin SDK v2.2 from the Downloads page. Source code customers can also get the latest from our Github repository as well as from Cocoapods for iOS, and Maven for Android. We also keep on delivering continuously for bug fixes, features and minor updates to the following package sources.
In addition, our example code is published to Github and is available to clone or download.
Download SciChart iOS/Android / Xamarin v 2.2
The post SciChart iOS /Android / Xamarin v2.2 released! appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.
Read more »
We are pleased to announce the release of SciChart v5.1.1 Build 11473 . This is a minor update which contains a huge number of bug fixes. It is strongly advised for users of SciChart v5.x to upgrade to this version, which is a drop-in replacement.
What’s New in SciChart WPF v5.1.1?
There are bazillions of bug fixes and improvements made in touch screen feature, resampling, heat maps, export, and many more in SciChart v5.1.1. Please read on to see what is new in version 5.1.1.
Updated all C++ projects to v141 tools, latest Windows SDK. Required after build server upgrade. This is a breaking change for customers who compile from source-code. All other users unaffected.
- Fixed: DirectX renderer bug, unfilled columns when using a logarithmic Y axis
- Fixed: the issue in Multipane when it would crash at attempt to set negative height to a pane
- Fixed: GetColumnWidth method in BaseColumnRenderableSeries when the PointSeries can be null
- Fixed an issue when Xyz dataSeries go  values after calling [ToDiscontinuousSeries()] method
- Fixed: GetColumnWidth method in BaseColumnRenderableSeries when it returns wrong column width for hittest when columns go not one by oneAllow Scichart2D to work on D3D Level 10.0 hardware
- SC-4493 3D Styling Fixed: axis titles look differently than axis labels by default
- Fixed: 3d shadow on bottom problem, adding ability to control lighting:
- in the grid shaders, the cell color override should be done before lighting
- add a new parameter to control lighting factor is used, default it to 0.8 as it was hardcoded in shaders
- fix the bug in the bottom shadows test, marking the nulls with a value, and overriding the cell color to e transparent on them
- in the palette provider example, add a slider to control lighting about, defaulting it to zero so it remains looking the same
- Fixed: XyzDataSeries3D PointMetadata3D when it does not working for scaling or Color
- Fixed: bug where setting ImpulseRenderableSeries3D.StrokeThickness=0 causes a NullReferenceException
- Added: tests for DataSeries3D DataSeriesChanged event
- Added: Flags attribute to DataSeriesAction enum
- Fixed: updating metadata in XyzDataSeries3D
- Fixed: OnDataSeriesChanged in BaseGridDataSeries3D
- Fixed: 3D chart with MVVM
- SC-4475 Fixed: YAxisDragModifier doesn’t change ZoomState on surface
- Fixed: Lightning settings in 3D Uniform Orthogonal Heatmap Chart
- SC-4468 Fixed: DiscontinuousDateTimeAxis Rollover Modifier Not Displaying correct Xaxis Data – fixed CoordinateCalculator
- Fixed: adding labels to 3D chart
- Fixed: 3D Charts Not Rendering
- SC-4461 Fixed: XyzDataSeries3D always create a list of metadata filled with Nulls
- add Unit tests for operation with Metadata in XyzDataSeries3D
- add operation Insert and Remove for Metadata
- SC-4463 Fixed: PointMetadata3D cannot change VertexColor via the property
- SC-4464 Fixed: RenderableSeries3D DataSeriesChangedEventArgs.DataSeriesAction
- SC-4447 Fixed: Remove unnecessary firing of SelectionChanged event in PointMetadata3D (Selection event fired 100s of times when deselecting many points in a 3D Chart).
- Fixed: not changed _scrollBarMaXRange when SciChartScrollbar calls UpdateRange() with binding to DataRange
- Fixed: custom modifiers not working with touch
- SC-4552 Fixed: the extreme context must set the current buffer to last used, this will ensure the drawing order when a different buffer is used
- SC-4552 Fixed: do not call CheckSubbmitBuffer here because it changes the expected drawing order
- Fixed the issue when VerticalSliceModifier would crash if any other modifier set the RolloverMarkers property
- SC-4466 Fixed: Investigate Scrollbar behavior reported by a customer
- SC-4548 Fixed: when CategoryDateTime and CategoryNumericAxis do not react to the ZoomExtentsModifier
- Updated PointMetadata documentation
- Added: DragStarted and DragCompleted unsubscribes for annotation adorner markers
- SC-4516 Fixed: TooltipModifier and StackedSeries issue
- SC-4535 Fixed: the issue when CategoryCoordinateCalculator would not find some date values in the BaseXValues collection due to rounding errors;
- SC-4501 Fixed: the issue when CategoryNumericAxis would have default range of (0,10)/ Changed it to (0,1) as in CategoryDateTimeAxis
- SC-4509 Fixed: AxisDragModifier when it doesn’t set ZoomingState on Scale mode
- SC-4474 Fixed: ZoomHistory doesn’t record the first change
- SC-4458 Fixed: incorrect resampling results caused by how DateTime is implemented in .NET ( it’s a struct with long value but it uses 2 last bits for internal flags and the rest is used for storing Ticks );
- SC-4497 Fixed: AxisBase.DataRange gets calculated incorrectly for StackedSeries
- Added: DiscontinuousAxis and DoubleScaleDiscontinuousAxis obey CursorTextFormatting
- Fixed: the issue when Cursors XAxis label on DoubleScaleDiscontinuousAxis would be formatted differently than XAxis labels
- Improved: cursor label formatting for DoubleScaleDiscontinuousAxis
- Fixed: The export with CustomPointMarker in v5 not working
- Added: the Precision property; fixed a couple of issues in ColorPalette
- Removed: unused resources from the Realtime Heatmap example
- SC-4479 Fixed: the issue when the ExtremeScatterRenderableSeries’ markers are clipped incorrectly;
- SC-4458 Fixed: incorrect resampling of DateTime values which was caused by internal structure of DateTime in .Net
- added separate DateTime stuck on C++ side which applies mask to get correct Ticks value on C++ side; made some code refactoring;
- updated code for tests to cover the new case when using dates with local time;
- SC-4462 Fixed: Added a missing property for AxisCoreViewModel (NumericAxisViewModel missing IsStaticAxis flag)
- Added GetSprite method to BitmapSpriteBase
- Added: some minor template changes to DoubleScaleDiscontinuousDateTimeAxis and one more panel for common Xaxis in SciChartMultiPane template
- Updated: minimum requirement to .NET4.5.0 for installer
- SC-4454 Fixed: Added the ModifierSurface option to AnnotationCanvas
- SC-4451 Fixed: “Ensure Pie/Donut chart doesn’t create Storyboards / run animation when labels aren’t shown”
- do Animation for segment’s label if it is needed only for Donut chart
- do Animation for segment’s label if it is needed only
- SC-4438 Fixed: slowing chart rotation with a few series due to LegendModifier
- Added creation of ColorMap by default
- SC-4455 Axes for MVVM and export gets not exported
- Fixed: Software crashing due to an exception generated in SciChart.Drawing.DirectX
- Fixed: Contours 2D example to fit the DirectX Contouring mechanism
- Added GetSprite method to BitmapSpriteBase
- SC-4421 Fixed: DiscontinuousAxis range issue for GetClosestDateToSmaller if baseDate is in the end of the day.
- SC-4449 Fixed: Contours 2D example – add an option to hide heatmap
- SC-4436 Fixed: issue Stacked Column chart v5.1.0 missing one column
- SC-4448 Fixed: DateTimeAxisViewModel does not fire VisibleRangeChanged event
- Fixed the issue when DiscontinuousDateTimeAxis would break bindings to the calendar (#1309)
- SC-3962 Fixed: Export to XPS fails from Dev Mode toolbar in v4.2.2
- Fixed: the property name in binding for Axis MVVM
- Fixed: RolloverModifier behavior on column series when it isn’t within data bounds
- SC-4446 Fixed: Issue when VerticalLineAnnotationMVVM + styleKey causes exception
- SC-4443 Fixed: ScatterSeries (PointMarker) regression – points appear not filled
- Fixed: the issue of crashing scichart when using float type for data (throwing ArgumentException)
- Fixed: the type of hitTestInfo.Y1Value.
- Fixed: the issue of crashing scichart when using float type for data
- SC-4433 Fixed: When UseInterpolation=True and tooltipmodifier, the PointMetadata index is always previous, not nearest- added checking if seriesInfo has appropriate Metadata
- SC-4442 Fixed: Zoomhistory(TimeSpan animation duration) causes exception
- SC-4439 Fixed: When SelectedPolintMarker set in MVVM, all data-points disappear
- Fixed: NullReferenceException for GrowBy in some series viewmodel types
- Fixed: bug in CategoryDateTimeAxisViewModel with wrong ViewType
- SC-4440 Fixed: When Annotations MVVM labels do not display
- Added: new Properties for AxisCoreViewModel and some default values
- Fixed: an Exception while adding Axis via MVVM
- Fixed: error in CustomTooltipsWithModifiers example where AxisLabelStyle is applied to CursorModifier not Axis
- Added AxisPanelStyle to AxisBase.
- Added DefaultStyleKey to AxisPanel
- SC-4432 Fixed: StrokeDashArray does not work on Axis gridlines when DirectX11 renderer used
- Fixed: the problem with adding and removing StackedColumnRenderable Series using MVVM
Where to Get SciChart WPF v5.1.1?
SciChart WPF v220.127.116.1173 is available from:
Please ensure you uninstall the previous version(s) of SciChart before installing v5.1.1 as this can prevent some issues in the upgrade process!
GET SCICHART WPF v5.1.1
The post SciChart WPF v5.1.1 Build 11473 Released! appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.
Read more »
As of July 5th, 2018 we are going to change our NuGet nightly builds and package policy. Please read on to secure your previously integrated SciChart packages and set up future feeds correctly into your build system.
Why the change in Package Retention?
Over the years we have built up quite a library of tens of gigabytes of NuGet packages. Our host won’t allow us to increase the disk space any further without going onto a dedicated server plan, which would result in a NuGet feed URL change and disruption to our users. We want to keep it as less disruptive as possible, that is why we’re introducing a new package retention policy to tell you what builds will be kept and for how long.
- Important: From the 5th July 2018 onward, all nightly builds will be published to abtsoftware-bleeding-edge. See the this article to learn how to add this feed to your visual studio;
- Nightly builds will be kept for no longer than six months, or last 100 packages, whichever happens sooner;
- We encourage our users to use official release builds as we will be cleaning the feed from older builds.
Trimming older nightly builds
To preserve disk space we may start trimming older nightly builds in the v3 and v4 range, keeping official releases on the abtsoftware feed.
If you are using a nightly build we recommend using the latest (higher) official release as soon as possible. A list of official releases version numbers can be found at www.scichart.com/downloads in the right-hand column, please see below:
If you have any questions about how to ensure that your SciChart integration is seamless, please just contact us at support [at] scichart.com.
We are continuing to develop & support SciChart WPF and have some exciting new releases due soon. More to be announced in the near future!
The post NuGet Feed Nightly Build Retention appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.
Read more »
We stumbled upon the news recently that Xamarin.Forms 3.0 has preview support for WPF!
This is really interesting for us at SciChart, as we make iOS Charts, Android Charts with Xamarin Support, as well as WPF charts, but we do not yet have a UWP chart solution. We feel that the API for UWP is incomplete and too immature to make good charting components or applications, so have avoided too much investment into this platform until it showed more promise.
Well maybe we won’t have to? If WPF becomes a first class citizen of the Xamarin ecosystem, then this should really be the first choice for cross-platform development of Xamarin applications which require a Windows app footprint.
Find out more about Xamarin’s plans here.
We will be prototyping to see what we can do with these frameworks soon.
The post Xamarin Forms 3.0 Released, WPF support in preview appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.
Read more »
At SciChart, we pride ourselves on excellence in technical support and we want you to get a fast resolution to your requests.
In order to maintain an excellent level of service, as of May 2018, we have re-defined our support policy.
What are the Support Options?
SciChart customers may choose between packages with and without support. The no-support option comes with 90 days updates only. The Supported packages come with at least 1-year Priority Support and Updates. SciChart Professional product comes with and without support, and the SciChart Source-Code products always come with 1-year support.
If you require technical support, please find what is the best way and place to ask it in the flowchart below:
Here are handy links for you:
- To Submit a ticket to support team, please go here.
- To ask a question on StackOverflow with tag SciChart, please go here.
- To ask a question on SciChart Forum, please go here.
How do I do “X” with SciChart Questions:
- Say what version of SciChart you are using;
- Say what you want to achieve (screenshots, videos or diagrams if possible);
- Show what you have tried (code sample);
- Please ask for advice on your question clearly and cocisely.
- Say what version of SciChart you are using;
- Explain steps to reproduce, i.e. using our examples, or modifying one of our examples, or submitting your own code;
- Say what you have tried (if applicable);
- Do not put any proprietary information if you are sending it to bug-report at scichart.com
What does the Priority support Include?
*Subject to Fair Usage Policy
**We will respond to your request within 24-hours Monday-Friday 9am-5pm UTC.
What does not fall under the support scope?
The following is not in the scope of support, however, we are still happy to assist you where we can as a part of consultancy work:
- Creating a proof of concept for your project according to your requirements;
- Custom implementations, including providing assistance for unsupported features, new feature requests or use of the SciChart products setup outside of our guidelines;
- Speeding up development of the features logged for the future sprints;
- One to one direct contact with our development team over Skype or Teamviewer.
For all of the above, for corporate trial users and purchasing requests, please contact firstname.lastname@example.org.
What do you describe as Fair Usage?
In order to keep providing our legendary levels of technical support, we have instituted a fair-usage policy for our support services.
- If your volume of tickets or requests exceeds 10x the average. We reserve the right to delay or temporarily de-prioritize support.
- Professional and Source-Code customers will be prioritized over Trial.
- Bugs and feature requests will be prioritized based on the number of users they affect. Critical or wide-reaching bugs will always be given immediate attention.
Finally, with these changes, we hope to align ourselves with industry standards while continuing to provide an excellent level of support/service which is well above what our competitors provide.
The post Support Policy appeared first on Fast, Native Chart Controls for WPF, iOS, Android and Xamarin.
Read more »