Skip to content
New issue

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

Request: Expose more to the Low Level WASM #379

Open
MattiaTraverso opened this issue Nov 21, 2024 · 0 comments
Open

Request: Expose more to the Low Level WASM #379

MattiaTraverso opened this issue Nov 21, 2024 · 0 comments

Comments

@MattiaTraverso
Copy link

MattiaTraverso commented Nov 21, 2024

Hey,

I'm a senior dev working on a TypeScript game engine that uses Rive as the renderer. I'm having a blast, but I am puzzled as to why MANY different properties aren't exposed to the low level api.

  • Why can't I get a list of all bones. or at least a least of all bones that have been "exported"?
  • Why can't I reparent objects at runtime? (Ok, this one might be a little bit tricky)

But perhaps the most simple and yet the most important:

  • Why can't I access color fills?

Screenshot 2024-11-21 at 20 06 20
To my understanding, most of these (with the exception of the transform where you get the bone) are not exposed.

Rive is awesome because it saves time for the animator, but for simple things, it actually wastes time for the engineer.

Say I wanted my character to have a shirt that can have 10 different colours. Right now I have to ask my animator!
I think that a low level API should expose a simple fill, no?

I might be mistaken and there might be good reasons for this, but I thought I would ask.

Thanks in advance,
Mattia

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant