Notice: after bumping up to three 0.180.0 with @types/three 0.180.0,
Argument of type 'Group<Object3DEventMap>' is not assignable to parameter of type 'Object3D<Object3DEventMap>'.
Type 'Group<Object3DEventMap>' is missing the following properties from type 'Object3D<Object3DEventMap>': setPointerCapture, releasePointerCapture, hasPointerCapture
Currently, AFAIK, clearly, three, and @types/three doesn't have the setPointerCapture, releasePointerCapture, hasPointerCapture method / getters
The only place I found on GitHub, points out that https://github.com/pmndrs/xr/blob/456aa380206e93888cd3a5741a1534e672ae3106/packages/pointer-events/src/pointer.ts#L69-L100 declares
```js
declare module 'three' {
interface Object3D {
setPointerCapture(pointerId: number): void
releasePointerCapture(pointerId: number): void
hasPointerCapture(pointerId: number): boolean
intersectChildren?: boolean
interactableDescendants?: Array<Object3D>
/**
* @deprecated
*/
ancestorsHaveListeners?: boolean
ancestorsHavePointerListeners?: boolean
ancestorsHaveWheelListeners?: boolean
}
}
```
And in @tresjs/core v5, it uses the @pmndrs/pointer-events internally.
Somehow the Object3D from @types/three and the one augmented by @pmndrs/pointer-events are not compatible.
`new Object3D() as unknown as Object3D` works as workaround here but there should be no need to do such a thing since these two Object3D should be the same.
With no updates from `typescript`, I assume there is no breaking change or regression from `typescript` side.
* fix: replace hardcoded 'no voices available' and 'No voices were found...' message with localization key and remove duplicate pitch adjustment
* fix: add hint for custom voice entry in no voices available message
---------
Co-authored-by: 4meav <py96982015@gmail.com>
- Docs, base translation aand tamagotchi are now in Russian
- Russian language remapping in i18n modules
- Fixed en\settings.yaml
🍰
---------
Co-authored-by: Typed SIGTERM <typed.sigterm@gmail.com>
Co-authored-by: Neko <neko@ayaka.moe>
This commit introduces a new "OpenAI Compatible" provider, allowing users to connect to any service that implements the OpenAI API specification.
Previously, users were limited to the pre-defined list of providers. With the proliferation of many new AI services and local models (like LM Studio, vLLM, etc.) that expose an OpenAI-compatible endpoint, it has become impractical to add and maintain a separate integration for each one.
This new generic provider solves that problem by offering a single, flexible solution. It clarifies the user's choice by separating the official OpenAI service from other compatible alternatives, improving the overall user experience.
Closes#401, #388
Co-authored-by: Neko <neko@ayaka.moe>
---------
Co-authored-by: Neko <neko@ayaka.moe>
藍+85CD