We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be great if the library supported optional alternative text types for alternative use-cases.
For instance, one can imagine an instancedText based on THREE.InstancedMesh, to support fast-changing text.
One can also imagine a vectorText to support complex font that cannot be well rendered with MSDF, or that must be rendered very large with exactitude.
The architecture to support alternative text types is ready in TextManager
related : #11
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be great if the library supported optional alternative text types for alternative use-cases.
For instance, one can imagine an instancedText based on THREE.InstancedMesh, to support fast-changing text.
One can also imagine a vectorText to support complex font that cannot be well rendered with MSDF, or that must be rendered very large with exactitude.
The architecture to support alternative text types is ready in TextManager
related : #11
The text was updated successfully, but these errors were encountered: