Pre loader

1

Welcome to the SciChart Forums!

  • Please read our Question Asking Guidelines for how to format a good question
  • Some reputation is required to post answers. Get up-voted to avoid the spam filter!
  • We welcome community answers and upvotes. Every Q&A improves SciChart for everyone

WPF Forums | JavaScript Forums | Android Forums | iOS Forums

All Answers » Re: How to show loading state? » Comments for "Re: How to show loading state?"
  • Brad Taber
    This surface.renderSurface.renderedCallback property is removed in v3.0. How do we know when drawing has ended with v3.0?
  • Andrew Burnett-Thompson
    Hi Brad, there is a sciChartSurface.onSciChartRendered event instead. Check the members of ISCIChartSurface protocol here: https://www.scichart.com/documentation/ios/current/Protocols/ISCIChartSurface.html#/c:objc(pl)ISCIChartSurface(im)onSciChartRendered. Does this help?
  • Brad Taber
    Yes – thank you Andrew!
  • Brad Taber
    Andrew in working through this I don’t have it quite right. I am trying to call sciChartSurface.setRenderedListener(myViewController) so that my view controller’s implementation of onSciChartRendered will be called, however that doesn’t work. I am more accustomed to working with delegates, so if you can provide an example of how to properly listen for this event that would be great. Thanks!
  • Nazar Rudnyk
    hello Brad. Since it’s a block, you can’t implement it in your viewController, you must do that via closure\lambda or store that as a property\variable. I’ve updated the answer, so you might want to try it out. Best Regards, Nazar.
  • Brad Taber
    Thank you Nazar that was very helpful – I have my code all straightened out now. However I have a new crash earlier on in SciRenderSurfaceDrawable2D before I even get to my render callback. The last output in the console is: 2020-04-26 13:34:42.041085-0400 IT[41040:8653335] Series name: Low Alarm 2020-04-26 13:34:42.041486-0400 IT[41040:8653335] Series name: High Alarm 2020-04-26 13:34:42.041663-0400 IT[41040:8653335] Series name: Ambient °F Then I hit an EXC_BAD_ACCESS with the following stack trace: Thread 1 Queue : com.apple.main-thread (serial) #0 0x00000001047c59a0 in SCRT2DRenderingPipeline::Begin() () #1 0x00000001045ea0bc in -[SCIRenderSurfaceDrawable2D drawFrameIn:withDrawableSize:] () #2 0x00000001046ef3d0 in -[SCITwisterRendererBase drawFrameIn:withDrawableSize:] () #3 0x00000001046083c4 in -[SCIMetalRenderer drawFrameIn:withDrawableSize:] () #4 0x0000000104644e78 in -[SCIMetalRenderSurfaceBase draw] () #5 0x00000001a3457250 in -[CALayer display] () #6 0x00000001a34666e4 in CA::Layer::layout_and_display_if_needed(CA::Transaction*) () #7 0x00000001a33ab170 in CA::Context::commit_transaction(CA::Transaction*, double) () #8 0x00000001a33d5f7c in CA::Transaction::commit() () #9 0x00000001a09cbb2c in _afterCACommitHandler () #10 0x000000019c836668 in __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ () #11 0x000000019c831308 in __CFRunLoopDoObservers () #12 0x000000019c8318b8 in __CFRunLoopRun () #13 0x000000019c831084 in CFRunLoopRunSpecific () #14 0x00000001a6a7f534 in GSEventRunModal () #15 0x00000001a09a1670 in UIApplicationMain () Are you familiar with what may cause this crash? Thank you again for any suggestions on why this may be happening.
  • Brad Taber
    The above crash looks to be resolved in the 3.1 release. I was seeing it in 3.0, but no longer see it in 3.1.