Accessing state machine of nested artboard

Open
#188 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

No source files, tests, or entry points are named. Start by locating how the React runtime exposes nested artboards and their state machines, then determine whether the requested access is supported or requires a new API. Done means the intended nested-artboard state-machine workflow is clearly supported or explicitly documented.

Written by the indexing model from the issue text.

Description

triage

Hello! :)

Short background on what I'm working on:
I have a multiscreen setup on a wall where each monitor is attached to a single computer. The idea is to have a dynamic background animation that spans over all those monitors. Since I would love to have that dynamic with different triggerable transitions I'm currently looking into rive. Fallback option will be a video solution but then I loose the dynamic interaction/transitions...

Definitely love how easy it is to create animations and build state machines with rive! Current problem tho is:
I went the path of creating one big artboard that contains the different background animations for the whole wall. Also a state machine with different layers. Idea was to have an artboard for each screen that shows a specific area of the full composition, that I can export then. I used the full animation composition (scaled and moved to correct area) as a nested artboard for that. The only thing now is, that I need access to the state machine of the nested artboard. Didn't manage to do so in the app and haven't found a way programmatically yet.

Is this too much of a special case, or is that possible somehow?

Dominant language
TypeScript
Stars
1.2k
Forks
58
Avg merge
3h 23m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rive-app/rive-react

All issues in rive-app/rive-react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.