Custom Undo/Redo operation

Hi there,

Thanks for your inquiry.

Unfortunately, ZoomHistoryManager API doesn’t allow adding ranges manually. It had been designed to handle only ranges pushed during SciChartSurface lifetime. So if you want to fill the zooming history before a ZoomHistoryManager is attached to a SciChartSurface, the ranges won’t be added.

Could you please describe your use-case in more details? Maybe we will be able to suggest an alternative solution.

Best Regards,
Joeri

For some reason, I am still not allowed to add comments to your reply … so will add an answer

The ZoomHistoryManager would already be attached.

The use case is that we have buttons in our UI that set specific X and Y ranges on the axes when the button is pressed. We’d like to be able to undo/redo these ranges just like we can with Panning/Zooming.

e.g

• User pans
• Users zooms
• User clicks our custom “SetRangeCommand” button which sets a new X and Y Range
• User zooms
• User zooms

we’d like the 3rd user operation to be part of the undo stack.

    <s:SciChartSurface ZoomHistoryManager="{Binding ZoomHistoryManager }">
   <s:SciChartSurface.XAxes>
      <s:NumericAxis  VisibleRange="{Binding XVisibleRange }" />
   </s:SciChartSurface.XAxes>
</s:SciChartSurface>




    public class ViewModel
{
     public ICommand SetRangeCommand => SetRange();

     public ZoomHistoryManager ZoomHistoryManager { get; } = new();

     public DoubleRange XVisibleRange { get; set; }

     public void SetRange()
     {
         // we would like this to be an undo/redo step, just like how the chart modifiers work
         XVisibleRange = new XVisibleRange();   

         // ZoomHistoryManager.... Add Step?    
     }

}

Ok, I have this working now, turns out you can’t use the Axes Ids. You have to pass in the actual instance of the axis …

 ZoomHistoryManager.SaveLatestRange(new AxisKey(ZoomHistoryManager.ParentSurface.YAxes[0]), YAxisRange);
        ZoomHistoryManager.PushAll();

It would be great if there were clear examples for this stuff! .. I seem to waste a lot of time figuring it out by trial and error.