\r\n \u003CTresMeshNormalMaterial />\r\n \u003CHtml\r\n center\r\n transform\r\n :distance-factor=\"4\"\r\n :position=\"[0, 0, 0.65]\"\r\n :scale=\"[0.75, 0.75, 0.75]\"\r\n >\r\n \u003Cdiv>\r\n \u003Cp>This should not scroll\u003C/p>\r\n \u003C/div>\r\n \u003C/Html>\r\n \u003C/TresMesh>\r\n```\r\nI expect the first element to scroll, and the second to stay.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz\r\n Memory: 3.82 GB / 11.69 GB\r\n Container: Yes\r\n Shell: 3.6.1 - /usr/bin/fish\r\n Binaries:\r\n Node: 21.5.0 - ~/.local/share/nvm/v21.5.0/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 10.2.4 - ~/.local/share/nvm/v21.5.0/bin/npm\r\n pnpm: 8.14.1 - ~/.local/share/pnpm/pnpm\r\n bun: 1.0.7 - ~/.bun/bin/bun\r\n```\r\n\r\n\r\n### Used Package Manager\r\n\r\npnpm\r\n\r\n### Code of Conduct\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2896,2899],{"name":2897,"color":2898},"pending-triage","97A4FE",{"name":2900,"color":2901},"waiting for author","B145BC",507,"Native html scroll and @tresjs/cientos Html component behaviour","2024-03-30T15:37:07Z","https://github.com/Tresjs/tres/issues/507",0.7936348,{"description":2908,"labels":2909,"number":2917,"owner":2874,"repository":2875,"state":2876,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Describe the bug\r\n\r\n`useTresContext().controls.value` is null when using Cientos' `\u003COrbitControls>`.\r\n\r\n### Context\r\n\r\n[This issue was opened on Cientos.](https://github.com/Tresjs/cientos/issues/249) Part of the issue was addressed with a Cientos' PR. \r\n\r\nOpening an issue here to look into `useTresContext().controls`. \r\n\r\n----\r\n\r\n@zkobrinsky\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/tresjs-basic-fzdwdc?file=src%2Fcomponents%2FTheScene.vue\r\n\r\n### Steps to reproduce\r\n\r\n_No response_\r\n\r\n### System Info\r\n\r\n_No response_\r\n\r\n### Used Package Manager\r\n\r\nnpm\r\n\r\n### Code of Conduct\r\n\r\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/tres/blob/main/CODE_OF_CONDUCT.md)\r\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/tres/blob/main/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://tresjs.org/guide).\r\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/tres/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[2910,2913,2914],{"name":2911,"color":2912},"bug","d73a4a",{"name":2900,"color":2901},{"name":2915,"color":2916},"v4","7980EA",418,"useTresContext().controls.value is null when using Cientos' `\u003COrbitControls />`","2024-08-21T10:29:21Z","https://github.com/Tresjs/tres/issues/418",0.8017463,{"description":2923,"labels":2924,"number":2926,"owner":2874,"repository":2888,"state":2876,"title":2927,"updated_at":2928,"url":2929,"score":2930},"The current API is far from ideal, we initially followed the same DX as https://github.com/pmndrs/leva \r\nbut encountered number of issues\"\r\n\r\n- Need to use `value.value` for multiple controls #92 \r\n- Shared `useControls` composable, impossible to have multiple distinct instances #98 \r\n\r\nI will copy the different suggestions from @andretchen0 \r\n\r\n## Example: Tweakpane\r\n\r\n[Tweakpane | Bindings](https://tweakpane.github.io/docs/input-bindings/)\r\n\r\nTweakpane uses `.addBinding(stateObject, key, params)`.\r\n\r\n```ts\r\nconst PARAMS = {\r\n speed: 50,\r\n};\r\n\r\nconst pane = new Pane();\r\npane.addBinding(PARAMS, 'speed', {\r\n min: 0,\r\n max: 100,\r\n});\r\n```\r\n\r\nWith this setup, there's no need for a `watch` and so no `value.value`. The value is already being \"watched\" with the configuration above.\r\n\r\n## Example: v-tweakpane\r\n\r\nA variation of Tweakpane, this time with Vue. Like Tweakpane, it uses a specific method for creating a widget and binding at the same time. This avoids the need to `watch` and avoids `.value.value`.\r\n\r\n```ts\r\nconst onPaneTwoCreated = (pane: any) => {\r\n pane.registerPlugin(CamerakitPlugin);\r\n const PARAMS = {\r\n flen: 55,\r\n fnum: 1.8,\r\n iso: 100,\r\n };\r\n pane.addInput(PARAMS, 'flen', {\r\n view: 'cameraring',\r\n series: 0,\r\n unit: { pixels: 50, ticks: 10, value: 0.2 },\r\n min: 1,\r\n step: 0.02,\r\n });\r\n```\r\n\r\nThe [example](https://github.com/vinayakkulkarni/v-tweakpane/blob/main/example/src/App.vue) uses some callbacks for setup, which Leches doesn't need. Personally, I'd like to avoid having those.\r\n\r\n## Example: Vuetify\r\n\r\nIn this [Vuetify example](https://vuetifyjs.com/en/components/sliders/#min-and-max), most of the config that Leches does in `\u003Csetup>` is handled in `\u003Ctemplate>`. Bindings are created using `v-model` in the `\u003Ctemplate>`.\r\n\r\n```html\r\n\u003Ctemplate>\r\n \u003Cv-slider\r\n v-model=\"slider\"\r\n class=\"align-center\"\r\n :max=\"max\"\r\n :min=\"min\"\r\n hide-details\r\n >\r\n \u003Ctemplate v-slot:append>\r\n \u003Cv-text-field\r\n v-model=\"slider\"\r\n hide-details\r\n single-line\r\n density=\"compact\"\r\n type=\"number\"\r\n style=\"width: 70px\"\r\n >\u003C/v-text-field>\r\n \u003C/template>\r\n \u003C/v-slider>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\n export default {\r\n data () {\r\n return {\r\n min: -50,\r\n max: 90,\r\n slider: 40,\r\n }\r\n },\r\n }\r\n\u003C/script>\r\n```",[2925],{"name":2885,"color":2886},104,"Rethink API and DX","2024-04-27T19:31:44Z","https://github.com/Tresjs/leches/issues/104",0.8019482,{"description":2932,"labels":2933,"number":2934,"owner":2874,"repository":2935,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the bug\n\n[`CameraControls`](https://cientos.tresjs.org/guide/controls/camera-controls.html) component ignores `mouseButtons` and `touches` properties.\n\n### Reproduction\n\nhttps://play.tresjs.org/#eNqdVttu2zgQ/RVCwSIPa1NynGS72nTh2r0gi80FtZ8a9YGWGIsJRRIk5dgI/O8dkr5IbpA6TQTDnDkzc3jIGfk5mmhqPiiF5zWN0ujC5Jopiwy1tUKciNn7LLImi/7NBKuU1BY9oyExLB+XpJBPV0R10Pjrl+FIcqnHiuS0g67lRAoKLsXEDK3QvZYVOralpvT4n0YeV3pExJyYLWhgwfZg4lzqNnZEKqrJSAqrJX8Bz6iw0jRCRqM1JPeR3Xwd6iCZgJWxaMbRe/ScCYRyTon2e0jR8dG7k4/D0dlxx3mM36dJkdU19RbCVUlSdE+4CYYAgf1Oloqm+/I4hKytqu1Oo3RfMweyO9HStobgXgHtizicDpwFLCytFCeWwgqhi4aW8+6UiQLObcb9uSH48/5bqo2iuWVzGuREqZKGWSYFoO/+7iD3fM8iFG/C9mRPK1kb2p3WFsgaCHpGnN7bFNTGH0aTy5tr/O3m5gqtmjlc6Stqyna17kkHwZO4cqmWlmwcSQddEVvi28vgXafZ7BFU+UJlRa1eopTomWNx1+ugHj7roH6TfKP0REoBSalmhKPcyQ5R62NuUo03Aa9zB4ruccVyYmw3XIB22aFcvMDTkdx8vInr6Wf3/xtcQWMn9c9KjlVJ9U7Lg5l8Hg6T/vCXTD4y7a6aFIT/z2al/UlBIHXqD58JSwW4luDo4ZO2qOsqoUa44GC4iBu3H5bGLrn7WtqKQ7NMZbEMfV2B8kykKIH2QUiRovDdFZYldcRS1EuSP7zhiRW23K5XmTiC/guJfoFFaEryx5mWtShg1Pg5cpQkrg6kgcb1BKNOFKZTtyIKPxgpYOT69NnaAZM2DQWdrTkNnSOLSmuVSeM4LwTEF5SzucaC2lioKm7CB318jntxwYyNnRnQWeTHTCtxGJtvyR0iIP1fONmlX5vbVewTJY+KiEO4b7GDU5xsiW+MuGIuppnbvU0OyetwA8h4ngDfP6mpmjLASw/m2cH6NuCDXoLPICNMWrrAVVvdNQ5usKbFGxKHgNdSA7Bb0IodkHQDdZs/xecxZ9MXU+69Hw/IvBcxOMHvcD+c2J4LV7Ko+e74XE3ohxU0gjUAumezvTbIZaUYp/pGuVHRbgfCuXz6z9u2L2MfU9L88QX7g1mE3dzCDaV6Dme8uz8wGKgN7k/ja7qA71tnYP2q8ys1kteOY4ANofGBdgPn2V76roaZMzGfFn7MrTfVImrhd4O33m1m8PaCB8N3L5zH+zswekWl3c76uL8VfPUDB9Q/3Q==\n\n### Steps to reproduce\n\n1. Add `PerspectiveCamera` to a scene\r\n2. Add `CameraControls` from `@tresjs/cientos`\r\n3. Pass `mouseButtons` prop using `camera-controls`' `ACTION` enum:\r\n ```\r\n import CC from 'camera-controls';\r\n ...\r\n \u003CCameraControls :mouse-buttons=\"{ left: CC.ACTION.ZOOM }\" />\r\n ```\r\n4. The camera should zoom on drag when left mouse button is pressed, but instead the camera rotates (default behavior)\r\n\r\n_Note:_ The same applies to `touches` as both of the props are discarded when turning props into refs, and aren't passed down to the extended component: https://github.com/Tresjs/cientos/blob/main/src/core/controls/CameraControls.vue#L331C1-L357C18\r\n\r\nI prepared a fix for that, will submit a PR shortly 😉 \r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 14.4.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 4.18 GB / 32.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node\r\n npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm\r\n pnpm: 8.15.4 - ~/Library/pnpm/pnpm\r\n bun: 1.0.27 - ~/.bun/bin/bun\r\n Browsers:\r\n Chrome: 124.0.6367.61\r\n Safari: 17.4.1\r\n npmPackages:\r\n @tresjs/cientos: ^3.8.0 => 3.8.0 \r\n @tresjs/core: ^3.8.1 => 3.8.1 \r\n @tresjs/leches: ^0.14.0 => 0.14.0 \r\n @tresjs/post-processing: ^0.7.1 => 0.7.1 \r\n vite: ^5.1.5 => 5.1.6\n```\n\n\n### Used Package Manager\n\nnpm\n\n### Code of Conduct\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/cientos/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/Tresjs/cientos/issues) that reports the same bug to avoid creating a duplicate.\n- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.",[],384,"cientos","closed","CameraControls component doesn't support mouseButtons and touches props","2024-04-22T19:21:04Z","https://github.com/Tresjs/cientos/issues/384",0.7536832,{"description":2942,"labels":2943,"number":30,"owner":2874,"repository":2875,"state":2936,"title":2947,"updated_at":2948,"url":2949,"score":2950},"**Describe the bug**\r\n\r\nDocumentation for events emitted by this component are missing\r\n\r\n- `dragging` event\r\n- `change` event\r\n- `mouseDown` event\r\n- `mouseUp` event\r\n- `objectChange` event\r\n\r\n**Reproduction**\r\nPlease provide a link using this template on [Stackblitz](https://stackblitz.com/edit/tresjs-basic?file=README.md) \r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to '...'\r\n2. Click on '....'\r\n3. Scroll down to '....'\r\n4. See error\r\n",[2944],{"name":2945,"color":2946},"docs","0075ca","Add events to TransformControls documentation","2023-01-07T18:45:57Z","https://github.com/Tresjs/tres/issues/64",0.76983005,{"description":2952,"labels":2953,"number":2955,"owner":2874,"repository":2875,"state":2936,"title":2956,"updated_at":2957,"url":2958,"score":2959},"**Describe the bug**\r\nSeems like the state of useTres keep alive between pages, even when the routes are lazy\r\n\r\n**Steps**\r\nSteps to reproduce the behavior:\r\n1. Go to https://serene-mousse-562782.netlify.app/MouseShaderEffect\r\n2. Move the mouse, observe no controls is on the scene\r\n3. Go to home using the navbar (here you can see we have the pam-camera-control)\r\n4. Return to the mouseShaderEffect using the navbar (observe now the state of pam-camera-controls remains)\r\n\r\nThis behavior also happens with orbicControls\r\n\r\n**Expected behavior**\r\nA new route should be a complete new canvas which also means that the old canvas should die entirely and every other effect\r\n\r\n**Additional context**\r\nThis could affect other states/effect throug the library\r\n",[2954],{"name":2911,"color":2912},173,"Problem with state using router navigation","2023-04-05T13:41:50Z","https://github.com/Tresjs/tres/issues/173",0.77681875,{"description":2961,"labels":2962,"number":1631,"owner":2874,"repository":2875,"state":2936,"title":2964,"updated_at":2965,"url":2966,"score":2967},"- [x] Orbit Controls (mention cientos approach)\r\n- [x] Basic animations\r\n- [x] Load Textures\r\n- [x] Load Models",[2963],{"name":2945,"color":2946},"Docs core examples","2022-12-12T10:19:32Z","https://github.com/Tresjs/tres/issues/20",0.7787048,{"description":2969,"labels":2970,"number":2971,"owner":2874,"repository":2935,"state":2936,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Description\n\nI added multiple scenes to one pages and added multiple `\u003CMouseParallax/>`component.\r\nProblem is, the ones after the first on top of tha page, had strange behaviour due to the fact that the component uses the position of the mouse in windows, not on the object. \r\nIIt may be useful to add a prop to let the component use its local position instead.\r\nAlso it could be nice to add the possibilities to configure also the `scroll`option of `useMouse`\r\n\r\nI never proposed nor pushed PR to OSS and i really would like to start, and this seems something easy (i already reimplemented it in a project)...\n\n### Suggested solution\n\nin `MouseParallax.vue` add a `local` boolean prop that then pass the option of the target to `useMouse()`\r\nThe prop should also enable `useElementSize()` as the source for `width`and `height` instead of `useWindowSize()`.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] I agree to follow this project's [Code of Conduct](https://github.com/Tresjs/cientos/blob/main/CODE_OF_CONDUCT.md)\n- [X] Read the [Contributing Guidelines](https://github.com/Tresjs/cientos/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://cientos.tresjs.org/guide).\n- [X] Check that there isn't [already an issue](https://github.com/tresjs/cientos/issues) that reports the same bug to avoid creating a duplicate.",[],397,"Local parallax, using local mouse coordinates instead of window one.","2024-05-05T13:39:55Z","https://github.com/Tresjs/cientos/issues/397",0.79580414,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuPQpj8efikmq8ycDfBS1q16jb1cGW4xVrPr6ylid97I":-1},"/Tresjs/leches/62"]