Question: onWheel x ref why not both?

I’m working on a small idea and I’m struggling with this little interference.

On my Stage I’m using onWheel={e => configs.handleWheel(e)}, but I’m populating an set of arrows (with map) on a layer using ref={node => execthis(node)}. Using both as this way I do not have access to “getStage()” it does not pass node => to the arrows. React Konva just breaks.

The point is, I do not want to use “state” (react) I want to do “.setPoints()” to the arrows, as it is already working. However, with onWheel it bugs/breaks. Works perfectly without onWheel. But then I lose the scrolling functionality.

Using “.setPoints()” I have less renders and gets more fluid.

What should I do?

Cheers.

[lavrton]

You may try to update react-konva to the latest version. It has changes in internal updating implementation https://github.com/konvajs/react-konva/issues/271.

Probably you will have the expected result. https://codesandbox.io/s/4jxyywwx4

[lavrton]

React will reset reference to null on every update. So I guess in you execthis you will need something like this:

if (!node) {
  return;
}