Same reference when getting points from two differents vtkPoints about vtk-js

[jourdain]

That is the expected behavior. The getPoint(idx) is only provided as a helper and we do not allocate new memory for each point coordinate, we reuse the same holder. We could put that holder within the instance instead of the module.

[laurennlam]

Thanks for the explanation.
I think it's confusing to have this behavior inside the module. I spent much time to understand what happens...
For me it's not intuitive because I'm thinking like in VTK, but I'm a beginner on javascript so maybe it's a normal behaviour.

[jourdain]

I didn't wanted to implement a getPoint(idx) initially as he lead to bad memory management.
I wanted to force users to use the native API on arrays.

But we made it so you could provide the tuple container.

So in you could write your code like that:

const p1 = [0,0,0];
const p2 = [0,0,0];

data1.getPoint(0, p1);
data2.getPoint(0, p2);

[jourdain]

Like in VTK

[laurennlam]

Yes, thanks a lot @jourdain !