Is there plans for better SwiftUI support?

Hi Tyler

There aren’t any plans at the moment to develop further SwiftUI views on top of SciChart.iOS

Users can still use SciChart in SwiftUI simply as follows:

1. Begin by declaring a SurfaceView struct, which conforms to the UIViewRepresentable protocol. Import SciChart, instantiate a SCIChartSurface, add axes, renderable series, and other elements to
   your SCIChartSurface.

2. Then we configure SCIChartSurface the old-fashioned imperative way.

3. Finally import this into your application

   import SwiftUI
   import SciChart
   struct SurfaceView: UIViewRepresentable {​​​​​​​​​​​​
   func makeUIView(context: Context) -> SCIChartSurface {​​​​​​​​​​​​
   let surface = SCIChartSurface()
   let xAxis = SCINumericAxis()

         xAxis.growBy = SCIDoubleRange(min: 0.05, max: 0.05)
         let yAxis = SCINumericAxis()
   
         yAxis.growBy = SCIDoubleRange(min: 0.05, max: 0.05)
         let count = 1000
         let xValues = SCIDoubleValues(capacity: count)
         let yValues = SCIDoubleValues(capacity: count)
         for i in 0 ..< count {​​​​​​​​​​​​
             let x: Double = 10.0 * Double(i) / Double(count)
             let y: Double = sin(2 * x)
             xValues.add(x)
             yValues.add(y)
         }​​​​​​​​​​​​
   
         let dataSeries = SCIXyDataSeries(xType: .double, yType: .double)
         dataSeries.append(x: xValues, y: yValues)
   
         let renderableSeries = SCIFastLineRenderableSeries()
         renderableSeries.dataSeries = dataSeries
   
         SCIUpdateSuspender.usingWith(self.surface) {​​​​​​​​​​​​
             self.surface.xAxes.add(xAxis)
             self.surface.yAxes.add(yAxis)
             self.surface.renderableSeries.add(renderableSeries)
         }​​​​​​​​​​​​
         return surface
     }​​​​​​​​​​​​
   
     func updateUIView(_ uiView: SCIChartSurface, context: Context) {​​​​​​​​​​​​}​​​​​​​​​​​​
   

   }​​​​​​​​​​​​

   struct ContentView: View {​​​​​​​​​​​​
   var body: some View {​​​​​​​​​​​​
   SurfaceView()
   }​​​​​​​​​​​​
   }​​​​​​​​​​​​

If you’ve hit problems (you mentioned Pointers) I would like to hear more about them, specific pain points and what you did to resolve them or work around them.

SciChart.iOS underneath uses Objective-C, which is required as we interface to C++ via Objective-C++. Some of these issues may be resolvable but others may not due to the tech stack.

Best regards,
Andrew