forEachComponent in rive 0.14.0-dev.3

[YannMarti]

Hello
I was checking out how to migrate to rive 0.14.0 and have noticed that you can not loop over components in the artboard anymore, is there a new way to do it? We need it for text run specifically so if there is a way to get all textruns without knowing their name, that would also work.

[YannMarti]

For reference, we use it to translate all the animations in the app with this function:

void localizeRiveAnimationText(Artboard artboard) {
  artboard.forEachComponent(
    (Component comp) {
      if (comp is TextValueRun) {
        comp.text = comp.text.tr;
      }
    },
  );
}

[HayesGordon]

Unfortunately, no. This was more easily accessible in the old runtime, as the code was mostly written in Dart.

The core runtime code is C++ now, and we use FFI to invoke the relevant code. Adding something like this won't be a trivial change and would be a big chunk of work, as we would also need to expose the different component types, for example TextValueRun.

You can read more about the change here.

Note that updating text runs in this manner is discouraged. The old runtime did not have access to newer features like Data Binding, which is significantly better for working with data and state, such as, updating text.

With data binding, you can access all the properties on a view model by doing viewModel.properties, which will allow you to see all the existing string components and translate them.

This will require you to update your .riv file to support data binding. If you need help with that, you can ask on our Community.

I'm closing this issue as unplanned, as we encourage all users to use data binding to get the most out of Rive and to ensure your graphics work well with upcoming features.

[YannMarti]

Hmm, was afraid that would be the case. Anyways, thanks for the quick response.