RangeControl -> CircularRangeBehavior

Hi everyone is my first post.
Fuse is very good tool. Good work Fuse team.

Fuse Version:
Fuse version 0.25.5 (build 7677)

I used CircularRangeBehavior and have problem on Log.
What I do wrong?
Please see log below.
Thank for help.

My Code


<RangeControl Width="100" Height="100"  HitTestMode="LocalBounds"  ux:Name="mySlider">
    <CircularRangeBehavior MaximumRadius="410" MinimumRadius="100"  StartAngleDegrees="100" EndAngleDegrees="410" />

 <DataBinding Target="mySlider.Value" Key="value"/>
    <Panel ux:Name="thumb" Margin="4">
        <Rectangle Color="Red" Alignment="Right" Height="20" Width="20" CornerRadius="4" />
    </Panel>

    <ProgressAnimation>
            <Rotate Target="thumb" Degrees="380" />
        </ProgressAnimation>
</RangeControl>

Log

Fuse.Controls.Native.iOS.InputDispatch.HandleEvent(ObjC.Object,Fuse.Visual,Fuse.Controls.Native.iOS.UIEvent)
       at Fuse.Controls.Native.iOS.InputDispatch.HandleEvent(ObjC.Object,Fuse.Visual,ObjC.Object)
       at Fuse.Controls.Native.iOS.GraphicsView.OnTouch(ObjC.Object,ObjC.Object)
    Object reference was null
LOG: Uno.NullReferenceException: Object reference was null
       at Fuse.Gestures.CircularRangeBehavior.OnLostCapture()
       at Fuse.Input.Pointer.GetHardCapturer(int)
       at Fuse.Input.Pointer.RouteToCapturer(Fuse.Input.PointerEventData)
       at Fuse.Input.Pointer.RoutePointerEvent(Fuse.Input.PointerEventData,Fuse.Visual)
       at Fuse.Input.Pointer.RaiseReleased(Fuse.Visual,Fuse.Input.PointerEventData)
       at Fuse.Controls.Native.iOS.InputDispatch.RaiseReleased(Fuse.Visual,Fuse.Input.PointerEventData)
       at Fuse.Controls.Native.iOS.InputDispatch.HandleEvent(ObjC.Object,Fuse.Visual,Fuse.Controls.Native.iOS.UIEvent)
       at Fuse.Controls.Native.iOS.InputDispatch.HandleEvent(ObjC.Object,Fuse.Visual,ObjC.Object)
       at Fuse.Controls.Native.iOS.GraphicsView.OnTouch(ObjC.Object,ObjC.Object)
    Object reference was null
LOG: Object reference was null
LOG: Failure state within a failed state. Simply ignoring that.

Hi, and sorry for the late reply. I can’t reproduce this in Fuse 0.28, so I assume it has been fixed since 0.25. Please let us know if you still get this problem after upgrading to 0.28.