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

Nested artboards loaded with empty name, makes their inputs inaccesible #433

Open
fpinzn opened this issue Nov 15, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@fpinzn
Copy link

fpinzn commented Nov 15, 2024

Hello! Thanks for creating such an amazing tool 🫶

Description

Nested artboards are loaded without a name, so their inputs become inaccesible (even when exposed to their parent artboards).

This is the result of inspecting the attached “arrow.riv”. See in the last line how after the arrow, the name of the nested artboard should appear but is empty (the “_name” field is also empty)
Screenshot 2024-11-15 at 1 16 24 PM

This doesn’t seem to happen with all files, “runtime_nested_inputs.riv” used for the example on how to use nested inputs in this repo works fine.

For comparison, inspecting that file looks like this (check the "CircleOuter" on the last line):
Screenshot 2024-11-15 at 1 18 14 PM

Steps To Reproduce

  1. Load any of the provided .riv files
  2. Inspect the file instance using the debugger

Source .riv/.rev file

rivs.zip

Expected behavior

The nested artboards should have the name so their inputs can be accessed.

Device & Versions (please complete the following information)

  • Device: iPhone 16
  • OS: iOS 18.0.1
  • Flutter Version:
Flutter 3.22.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b0850beeb2 (4 months ago) • 2024-07-16 21:43:41 -0700
Engine • revision 235db911ba
Tools • Dart 3.4.4 • DevTools 2.34.3
  • rive: 0.13.15
  • rive_common: 0.4.12
@fpinzn fpinzn added the bug Something isn't working label Nov 15, 2024
@plitarko
Copy link

plitarko commented Dec 9, 2024

I have the same issue

@cooljingle
Copy link

Could this be the reason? (found it after encountering the same problem)

Screenshot 2024-12-09 at 1 51 03 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants