1

The percentage of the available area that the bar should fill is indicated by this number, which ranges from 0 to 1. Though I had assumed the reverse, that appeared to be the only attribute that might work. It is quite helpful to set that to 1.

Hello,
This sounds as a nice improvement to make. But as of now I can only suggest using the CustomAnnotation for such cases. And I believe there is a way to deal with the resizing issue that you have mentioned.

Here is an example of creating a Scalable Custom Annotation:

  class ScalableAnnotation extends CustomAnnotation {
    private initialWidth: number;
    private initialHeight: number;
    private initialDiff: number;

    public update(
      xCalc: CoordinateCalculatorBase,
      yCalc: CoordinateCalculatorBase,
      xCoordSvgTrans: number,
      yCoordSvgTrans: number
   ): void {
     super.update(xCalc, yCalc, xCoordSvgTrans, yCoordSvgTrans);
     if (!this.initialDiff) {
       this.initialDiff = xCalc.visibleMax - xCalc.visibleMin;
       this.initialWidth = Number.parseFloat(this.svg.getAttribute("width"));
       this.initialHeight = Number.parseFloat(this.svg.getAttribute("height"));
     } else {
       const diff = xCalc.visibleMax - xCalc.visibleMin;
       if (diff !== this.initialDiff) {
       const width = (this.initialWidth * this.initialDiff) / diff;
       const height = (this.initialHeight * this.initialDiff) / diff;
       this.setSvgAttribute("width", width);
       this.setSvgAttribute("height", height);
       let borderX1 = this.getX1Coordinate(xCalc, yCalc) + this.xCoordShift;
       let borderY1 = this.getY1Coordinate(xCalc, yCalc) + this.yCoordShift;
       this.setAnnotationBorders(
         borderX1,
         borderX1 + width,
         borderY1,
         borderY1 + height
       );
      this.updateAdornerInner();
     }
   }
 }
}

// Adding an instance of Scalable Custom Annotation.
// Notice the ScalableAnnotation class used and sizing properties set on the SVG string
const customAnnotation = new ScalableAnnotation({
  x1: 5,
  y1: 6,
  xCoordShift: 0,
  yCoordShift: 0,
  horizontalAnchorPoint: EHorizontalAnchorPoint.Left,
  verticalAnchorPoint: EVerticalAnchorPoint.Top,
  svgString: `<svg width="100" height="100" viewbox="0 0 100 100" preserveAspectRatio="xMinYMin meet"><circle cx="50%" cy="50%" r="50" fill="blue"/></svg>`,
  isEditable: true,
  xCoordinateMode: ECoordinateMode.DataValue,
  yCoordinateMode: ECoordinateMode.DataValue
});

See the Pen
ScalableCustomAnnotation by SciChart.js Official (@scichart)
on CodePen.

Hello Mr. Nha,

Thanks for your inquiry.
We can recommend you using our Uniform Surface Mesh chart type. Please find the corresponding documentation article below:
https://www.scichart.com/documentation/win/current/webframe.html#The%20SurfaceMesh%203D%20Chart%20Type.html

Please note: to see the C# code sample you can switch to it on the “XAML / CS” tab control.

Additionally, to use SciChart WPF inside your WinForms application you can use a WinForms ElementHost control. Here you can find one of the examples:
https://www.wpf-controls.com/hosting-a-wpf-control-in-winforms/

Hope this helps.

With best regards,
Lex S., MSEE
SciChart Technical Support Engineer

Hi Ben,

We discussed your inquiry.
To change the zooming direction you can override the OverrideKeyboardAction() method and change ActionTypeProperty and XyDirectionProperty values.
Please find the default OverrideKeyboardAction() method implementation below:

        protected virtual void OverrideKeyboardAction(MouseModifier modifier)
    {
        if (ExecuteWhen == MouseModifier.None)
        {
            if (modifier == MouseModifier.Ctrl)
            {
                this.SetCurrentValue(ActionTypeProperty, ActionType.Pan);
                this.SetCurrentValue(XyDirectionProperty, XyDirection.YDirection);
            }
            else if (modifier == MouseModifier.Shift)
            {
                this.SetCurrentValue(ActionTypeProperty, ActionType.Pan);
                this.SetCurrentValue(XyDirectionProperty, XyDirection.XDirection);
            }
        }
    }

With best regards,
Lex S., MSEE
SciChart Technical Support Engineer

Hi Andrew,

Just checking in to see if you have any solution for this isssue

Thanks,

Pramod

Hi Jongbog Joung,

Thanks for your inquiry.
This is a known issue and it has been already fixed in the SciChart v8.0.0.27776 hotfix build.
Here you can find more information regarding our latest releases:
https://www.scichart.com/changelog/scichart-wpf/

Please try out the latest SciChart version and let us know your feedback.

With best regards,
Lex S., MSEE
SciChart Technical Support Engineer

I have also forwarded your question regarding server-side licensing to our JS team.

Please note that we recommend separating questions related to different platforms and posting them in the corresponding SciChart forums channels so they can be reviewed and answered faster.
Here you can find our JS forums channel:
https://www.scichart.com/questions/categories/js

With best regards,
Lex S., MSEE
SciChart Technical Support Engineer

Hi Mohamed,

Hope you are doing well!
I am glad to inform you that we have fixed the reported issue with unsorted data, and the changes are available in the recently published SciChart hotfix build v8.3.1.28072
Here you can find how to get it:
https://www.scichart.com/documentation/win/current/webframe.html#Getting_Nightly_Builds_with_NuGet.html

More details regarding our latest release are available on our Changelog page here:
https://www.scichart.com/changelog/scichart-wpf/

Please try out the new SciChart version and let us know your feedback.

With best regards,
Lex S., MSEE
SciChart Technical Support Engineer

thank you

This is a known issue due to the way we detect if the axis is in its default state. We are taking a look to see if there is a simple and safe way we can sort out.
Regards
David

Hi Suzanne,

Firstly, we recommend providing code to reproduce this error. You can share this with us in a codepen, or a codesandbox. Instructions on how to do this can be found here: https://www.scichart.com/blog/codepen-codesandbox-and-jsfiddle-support-in-scichart-js

Next, we also recommend trying that same code to reproduce against the latest version of SciChart: v3.3. The version you are using (v3.0) is not the latest and could have bugs or issues in it.

We will await your update with code to reproduce before providing further assistance.

Best regards,
Andrew

The result screen is missing so I am uploading it.

This task is now done and released as of version 3.2.575. SciChartVerticalGroup will now copy LayoutStrategies from the existing LayoutManager onto it’s SynchronisedLayoutManager so custom synchronised layouts will just work.

Regards
David