feat(core): allow using window as pointer events source

[acvigue]

Added a useWindowPointer prop to TresCanvas that states whether or not to use the window as the source of pointer events.

Closes #581

Added the prop to docs page, let me know if I'm missing anything 😄

[netlify]

✅ Deploy Preview for tresjs-docs ready!

Name	Link
🔨 Latest commit	e1184db
🔍 Latest deploy log	https://app.netlify.com/sites/tresjs-docs/deploys/6620d98c3f87620008e0a8da
😎 Deploy Preview	https://deploy-preview-583--tresjs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[andretchen0]

@alvarosabu @Tinoooo

What do you think about expanding the TresCanvas props here?

tres/src/components/TresCanvas.vue

Line 65 in 43cd1a4

useWindowPointer: undefined,

My take:

I'm completely on board with allowing additional ways for the system to get events.

But, rather than passing a boolean flag that has to be implemented by the system for this particular case, I'd prefer to invert the dependencies. E.g., define a default PointerEventSource and allow the users to optionally provide their own.

Maybe that's something that can wait though.

[alvarosabu]

Hi @acvigue the pR probably needs to be updated with the v4 pointer event changes, could you do it so we evaluate itadding it in the next iterations? cc @andretchen0

[andretchen0]

Closing here.

For #789 , we'll use dependency inversion to allow users to supply their own pointer.