React mouse interactions ignored or not working or broken

[butters16]

UPDATE: There was never really a problem here. My issue stemmed from creating multiple components with this chart-1 portion of <Chart id='chart-1' data={data1}/>. Making those ids actually unique for each component fixed my problem. Sorry for any confusion.

Below this line is a red herring

---

This example does not seem to support mouse interactions, either by default or by explicitly adding any of the following:

    chart.setMouseInteractions(true);
    chart.onBackgroundMouseMove(() => {console.log('here 0')});
    chart.onSeriesBackgroundMouseMove(() => {console.log('here 1');});
    series.setMouseInteractions(true);
    series.onMouseMove(() => {console.log('here 2')});

I move my mouse all over the chart, but never see any of my logs. I also never see a tooltip like I see on the most basic ChartXY example even though that code does not appear to do anything to make that work, which makes me assume it should be on by default: https://www.arction.com/lightningchart-js-interactive-examples/edit/lcjs-example-0000-lineSeries.html

Is this expected? Are others having the same issue? It just feel like something is fundamentally broken with the React approach, but I don't see any console logs indicating any errors, even with verbose web browser debugging.

Help or acknowledgment would be appreciated. Thanks in advance!

[butters16]

My problem seems to be related to create chart printing multiple times, but not because the component is rerendering, rather because something in the parent chain was being destroyed and recreated, causing a new instance of the component. I'm not quite sure yet why that would be a problem, but when I did some hard-coding to work around that, the component started responding to mouse controls: tooltip and my console statements of here 0 and here 1.

I'm closing this issue, but I'll continue to research and post if I come up with anything new, like a different approach. I'm confused why this would be a problem and curious why the destroy chart log never appeared. I'm wondering if that would have helped with some cleanup and reassignment of event handlers.

[butters16]

I wonder if this comment in the code is because somebody brushed up against something similar 🤔.

// NOTE: console log is used to make sure that chart is only created once, even if data is changed!