1

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

Is your question related to WPF (Windows charts) or JS (JavaScript charts)?

In SciChart.js there is a mechanism to get a callback on legend checkbox changed. See the LegendModifier documentation.

Subscribing to Checkbox Checked Changed

As well as subscribing to BaseRenderableSeries.isVisibleChanged, you
can now subscribe to LegendModifier.isCheckedChanged event. This can
be done either in the constructor options to LegendModifier or after
creation.

const legend = new LegendModifier({
      showCheckboxes: true,
      showSeriesMarkers: true,
      showLegend: true,
      // Subscribe to checked changed here
      isCheckedChangedCallback: (series, isChecked) => {
          console.log(`Option 1: Legend item ${series.type} isChecked=${isChecked}`);   
      }
  });
  // Or here after instantiation
  legend.isCheckedChanged.subscribe((args) => {
      console.log(`Option 2: Legend item ${args.series.type} isChecked=${args.isChecked}`);
  });
  // Add the legend to the chart
  sciChartSurface.chartModifiers.add(legend);
  

Hi Yu Dexiu,

Thanks for your question.
There isn’t such a callback on the LegendModifier.

However, since Legend checkboxes can hide or show a RenderableSeries, you can subscribe to IsVisibleChanged event on a RenderableSeries. It will be fired when a user changes series visibility through the Legend.

Alternatively, you can re-template the default Legend and have a binding on Checkboxes that will be triggered when they are checked/unchecked.

You can find more info about Legend customization here:
https://www.scichart.com/documentation/win/current/webframe.html#LegendModifier.html

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

For server side licensing, the underlying component is in C++ and can be integrated into other languages and run on linux. We are currently working on improving the api and examples for this. Detailed questions on this need to be submitted on support.scichart.com as there are additional contractual requirements.
Regards
David

Thank you for getting in touch. The first thing we tend to ask for is steps or code to reproduce issues.

For SciChart.js (JavaScript) this can be created as a Codepen or CodeSandbox (here’s how).

This makes it really easy to share with the tech team & resolve problems fast.

Thanks for your understanding! We look forward to hearing back from you.

Hello Max, we are investigating the error on our side and here are some updates on the issue.
The error occurs specifically with Next 14.1, and seems to be related to module resolution during compilation. Specifically while compiling CommonJS modules. (BTW, running the boilerplate app in dev mode with “–turbo” seems to work fine)

Unfortunately, SciChart sources are built in CommonJS, and the library doesn’t support ES Modules, at the moment. (v3.3.570)

But the recently released library version provides a bundle with ESM support – “scichart/_wasm/scichart.browser.mjs”.

So as a temporary workaround you could use it like this:

import { SciChartSurface, NumericAxis } from "scichart/_wasm/scichart.browser.mjs";

To enable type checking you may add

import * as SciChartValue from "scichart/_wasm/scichart.browser.mjs";
import * as SciChartType from "scichart";
const SciChart = SciChartValue as typeof SciChartType;
const { SciChartSurface, NumericAxis } = SciChart;

We will be posting updates here. And, let us know if that works on your side.

Hi Ziv,

We discussed your inquiry.
Unfortunately, SciChart doesn’t provide this behavior out of the box.

However, it can be implemented on the user side by overriding the PerformScale(Point currentPoint, Point lastPoint, bool isSecondHalf) method of the YAxisDragModifier.
This method is called on every MouseMove event and calculates a new VisibleRange for an Axis based on the dragged distance. Please take a look:
https://www.scichart.com/documentation/win/current/webframe.html#SciChart.Charting~SciChart.Charting.ChartModifiers.AxisDragModifierBase~PerformScale.html

The default implementation is straightforward:

        protected virtual void PerformScale(Point currentPoint, Point lastPoint, bool isSecondHalf)
    {
        var axis = CurrentAxis;
        var scaledRange = CalculateScaledRange(currentPoint, lastPoint, isSecondHalf, axis);
        axis.VisibleRange = scaledRange;
    }

so you should just calculate the VisibleRange according to your desired behavior and assign it to the axis.VisibleRange instead of the scaledRange.

Hope this helps.

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

Hello, I have the same problem, I see that Maksim described it in great detail,
I’m using the latest version of SciChart (v8.3.0.28019), TargetFramework net7.0-windows.
Could you please take a look at this issue.

Hi Andrew,

Thank you for your answer!

In our case, we do not want to clip the visible range. What I am trying to achieve is the following: I have a series with some number of data points. Let us assume that in this series the lowest value is 67 and the highest value is 71. If we plot this normally with autorange = once, it will auto-range the Y axis to the visible range (67, 71). What I would like is to use the autorange feature so it automatically calculates the maximum range of Y axis but I would like to minimum range for Y axis to be 0 not 67 when we use ZoomExtentsModifier. The rest of the behaviors I do not want to affect: zooming, panning, dragging. What I am trying to say is that when I play with the zoom I do not want to restrict it. For example, if I play with the zoom I would like the range to modify to let’s say (68, 70) but also (-20, 100) (no clipping). But when we double-click the chart to trigger the ZoomExtentsModifier I would like to visible range to go to (0, 71) instead of (67, 71).

I am in an MVVM environment.
As I said in my comment I got it working the way I want by taking advantage of the GrowBy property. What I did was:

DoubleRange dr = axis.GetMaximumRange().AsDoubleRange();
axis.GrowBy = new DoubleRange(dr.Min / dr.Diff, dr.Max * 0.1 / dr.Diff);

This ensures that we have a 0 value as the min value of the visible range and we have a padding of 10% on the maximum side when we trigger the ZoomExtentsModifier. When I did this, I was not in an MVVM environment and I was using the NumericAxis type.

Since then, I moved to an MVVM environment and I am now using the NumericAxisViewModel type instead. But now, with this type do not have access to the GetMaximumRange() function. I need this function because in my example above it would return the visible range computed by the auto range which would be (67, 71).

Is this something we could achieve?

Hello Nicolas,

As for your question, I’ve investigated it and here are some results:
[1] First of all, MeasureXYAnnotation is the custom Annotation that is not part of SciChart library. The purpose of this in our official SciChart.Examples.Demo is to demonstrate the possibility and flexability of creating custom types of annotations based on our existing ones.
This Annotation was made without supporting MvvM, as it wasn’t a requirement for the exact example.

[2] You can try to implement your custom annotation ViewModel and add the Update() logic there
– You can start with this documentation:
https://www.scichart.com/documentation/win/current/webframe.html#Tutorial%2007b%20-%20Adding%20Annotations%20with%20MVVM.html
*** Note that your annotation(real one not viewModel) should be derived from CompositeAnnotationForMvvm not just CompositeAnnotation(to save all the style bindings for all properties)

public partial class MeasureXyAnnotation : CompositeAnnotationForMvvm

• The next thing will be to store somehow an object of real one annotation(you can use different ways to achieve this by using Interfaces etc)
• Then you’ll have to create a method that will call Update()method functionality on ‘a real’ annotation that is stored inside it. Simple method that will get two doubles as a parameters and set’s it accordingly to the X2Y2 props

***** Also you might need to use the AnnotationCreationModifierViewModel
For general idea you can take a look at our TradingAnnotations implementation.

If you still have questions regarding implementation, please ask.

I have tried the dynamic way by overriding getDataPointWidth and it did fix the problem where the data points were sparse but broke (showing overlapping bars) for other scenarios where it used to work before the fix.

When the background color is white (0xFFFFFF), colors with low Alpha values ​​appear very blurred or invisible in FastLineRenderableSeries. On the other hand, FastColumRenderableSeries shows clearly well even in colors with low alpha values. Please check again.

Hi,

I tried the same code above provided, but I am unable to reproduce the issue.
Can you please share screenshot of your result.

Here is the screenshot of my result.