Fix issue 22 - ARSCNViewDelegate Handling Content Updates

[farandal]

For review,

This is the solution that worked for me
#22

Cheers!

[farandal]

@boundsj

[boundsj]

Thanks!

In addition to the changes I requested, it'd be great if you added some example usages of these new protocol methods in the demo app.

[boundsj]

I think we should use s/MBRender/renderer in all of these new methods.

[boundsj]

This will cause a crash if the delegate is not nil but does not implement this method. This and all other calls should not force unwrap and should use optional chaining instead. MBRenderer should be changed to renderer here at the call site, too, after you make the change noted above.

[farandal]

Hello @boundsj,

I have changed the implementation approach.
I personally don't like very much the Idea that the AnnotationManager implements the ARSCNViewDelegates as part of the MapboxARKit, as I cannot implement the ARSCNViewDelegates later in the View. What I did additionally to your review, is basically delegate different methods that notify the Anchor detection updates depending on the type of the the Anchor, in this case ARAnchor and MBARAnchor. Maybe there is a better way to implement this, but for now, this works for me.

[farandal]

class ViewController: UIViewController, ARSCNViewDelegate, AnnotationManagerDelegate {
...

func renderer(_ renderer: SCNSceneRenderer, addedNode: SCNNode, arAnchor: ARAnchor) {
    //print("Added Node Notification, Native ARSCNViewDelegate delegated from Anotation Manager for ARAnchors")
}

func renderer(_ renderer: SCNSceneRenderer, addedNode: SCNNode, mbAnchor: MBARAnchor) {
    print("Added Node Notification, delegated from MB Anotation Manager for MBARAnchors")
}

...
}