Interaction is not working as intended (anymore)

[vatro]

This is due to several major / braking changes made like using context etc. -> fix /polish! (shouldn't be a big pain 🤞)

• All interactive components should push the created three.js instance (or better the self-reference? ) to canvas.raycast: RaycastArray (accepts three.js object instances and svelthree component references, references are being automatically replaced by corresponding three.js object instances on push) -> 1.0.0-next.0.43
• Current approach raycasts on pointer movement only. While this is ok / sane (performance) with static scenes, it's not working with moving objects + if pointer is not moving -> find another solution for this! -> probably raycast on every frame (if pointer is over canvas) for animated scenes (scenes being rendered every frame) and on mouse movement (if pointer is over canvas) with static scenes (scenes being rendered only once). -> 1.0.0-next.0.43
• Close Implement WebGLRenderer component mode "auto" #64
• Close Check/fix 'WebGLRenderer' component's modes 'always' & 'auto' + interaction #63.
• Create sophisticated test scenes: check (again) all pointer events with static and moving objects incl. all WebGLRenderer component modes:
  detected issues:
  • Recognize component references deeply nested inside an object provided as function argument svelte-accmod#2
  • Hoisted values passed to slots cause unneeded component updates svelte-accmod#3

[vatro]

With the latest major refactor: f20757f interaction is working better than before + is a completely different concept. I've also created quite a few new test scenes which still need to be 100% polished, but that's a separate issue, so closing this one.