rive-app / rive-app/rive-unity
[Feature Request] Expose ViewModel Change event
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 205
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Submission checklist
- I have confirmed the issue is present in the latest version of the Rive Unity package
- I have searched the documentation and forums and could not find an answer
- I have searched existing issues and this is not a duplicate
Description
To reduce errors, our project has created strongly typed wrappers around the Rive view models in the game. However a common issue we face is that game logic can bind a new instance of a view model, leading to stale references to view models.
This isn't generally a problem when simply retrieving or setting values as our wrappers reobtain the root view model instances from the state machine each time, however we haven't found a good solution to ensuring that events such as OnTrigger and OnChange are always subscribed to the latest version of a property.
Previous working version
No response
Reproduction steps / code
No response
Upload your reproduction files / stack trace
No response
Source .riv / .rev file
No response
Screenshots / video
No response
Unity Editor log file
No response
Rive Unity package version
v0.4.5
Unity version
v6000.5.0f1
Target platform
macOS
Editor OS & version
macOS Tahoe 26.5.2
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by tracing how Unity ViewModel instances are rebound and how existing OnTrigger and OnChange subscriptions are exposed; define the required change event behavior and verify that subscribers receive updates for the latest bound ViewModel instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100