Problems with using rive assets with nested art

Fermée
  • Quelque chose ne va pas ?
#296 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
react-native, typescript
Domaine
mobile-dev

Piste de recherche

Start with the linked repro, comparing its parent-artboard and nested-artboard tabs across iOS and Android. Read useSetRiveRenderer.ts and investigate the reported scrolling, click, button-state, and virtualized-node input behavior. Done means the listed issues no longer reproduce with nested art assets on the affected native platforms.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Description

Rive assets with an artboard that leverages nested artboards have a couple of issues.

IOS

  • Scrolling on lists is not as smooth (best perceived when slowly scrolling)

Android

  • Click events are not firing nearly as often as they should be
  • Can not hold and keep buttons depressed (possibly related)

Both Platforms

  • Nodes below the fold (likely those caught in virtualization) sometimes don't have their inputs set.

These problems are not observed with rive assets that don't use nested artboards or when directly using the nested artboard as opposed to the parent artboard.
None of these issues exist on web either.

Provide a Repro

https://github.com/GibbyBox/repro-nested-artboard-native-issues

Source .riv/.rev file

.riv committed in repro
ui_nodes.rev.zip

Device & Versions (please complete the following information)
  • Device: Iphone 15 Pro Max, Google Pixel 7a
  • OS: iOS 18.3.1, Android API level 34
  • NPM Version: 10.5.2
Additional Context

The provided repro has two tabs - one where I use the parent artboard and one where I instead use the nested artboard. I've also tested and can confirm this issues exists on all rive rendering engines (can be configured in useSetRiveRenderer.ts)

Langage dominant
TypeScript
Étoiles
789
Forks
81
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de rive-app/rive-react-native

Toutes les issues de rive-app/rive-react-native

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.