Text

⚠️ DEPRECATED: Use Data Binding instead of direct text run manipulation at runtime

DEPRECATION NOTICE: This entire page documents the legacy Text manipulation system. For new projects: Use Data Binding instead. For existing projects: Plan to migrate from direct text run manipulation to Data Binding as soon as possible.

For more information on designing and animating Text, please refer to the editor’s text section:

Text

Information on designing and animating Text

Read/Update Text Runs at Runtime

⚠️ LEGACY CONTENT WARNING: The following sections document the deprecated Text manipulation system. This content is provided for legacy support only. New implementations should use Data Binding.

If you intend to update a text run at runtime it’s important to manually enter a unique name for the run in the editor:

And then export the name: right-click and select Export name

You can identify an exported component if it’s surrounded by square brackets. This makes it possible for the run to be “discoverable” at runtime by its name. For more information, see Exporting for Runtime.

If the name is not set manually in the editor the name will not be part of the exported .riv (to reduce file size).

Text runs can also be updated on components at runtime, see Read/Update Nested Text Runs at Runtime below.

New Runtime (Recommended)

Setting Text via Data Binding

This functionality is deprecated. We recommend using Data Binding for controlling text.

export default function TextRunExample() {
    const { riveViewRef, setHybridRef } = useRive();
    const { riveFile } = useRiveFile(
    require('../../assets/rive/hello_world_text.riv')
    );

    useEffect(() => {
    if (riveViewRef) {
        try {
        console.log(riveViewRef.getTextRunValue('name'));
        riveViewRef.setTextRunValue('name', 'React Native');
        console.log(riveViewRef.getTextRunValue('name'));
        } catch (err) {
        console.error(err);
        }
    }
    }, [riveViewRef]);

    return (
    <View style={styles.container}>
        <View style={styles.riveContainer}>
        {riveFile ? (
            <RiveView
            style={styles.rive}
            autoPlay={true}
            fit={Fit.Contain}
            file={riveFile}
            hybridRef={setHybridRef}
            />
        ) : null}
        </View>
    </View>
    );
}

Legacy Runtime

Setting Text via Rive Ref

To set a given text run value at any given time, reference the .setTextRunValue() API on the Rive ref:

setTextRunValue: (textRunName: string, value: string) => void;

Supply the text run name and a second parameter, textValue, with a String value that you want to set the new text value for.

Example Usage

export default function DynamicText() {
const riveRef = useRef<RiveRef>(null);

const handleInputChange = (e: string) => {
    // Set the TextRun value of the 'name' TextRun
    // The name must exist else an error will be thrown
    riveRef.current?.setTextRunValue('name', e);
};

return (
    <SafeAreaView style={styles.safeAreaViewContainer}>
    <ScrollView>
        <Rive
        ref={riveRef}
        resourceName="hello_world_text"
        stateMachineName="State Machine 1"
        />
        <TextInput
        onChangeText={handleInputChange}
        defaultValue="world"
        />
    </ScrollView>
    </SafeAreaView>
);
}

Read/Update Nested Text Runs at Runtime

⚠️ DEPRECATED FEATURE: Nested Text Runs are part of the legacy Text manipulation system. Use Data Binding instead for controlling component text properties at runtime.

It’s possible to set nested text runs at runtime—text that is not on the main artboard but on a Component. To set a nested text run, you’ll need to take note of the path where the input exists at an artboard level.

For example, to get/set the text run named button_text on the Button artboard, you need to provide the correct path.

Setting Nested Text Runs

The artboard names here are:

• Main -> NestedArtboard -> Button

However, the path is determined based on the names set in the hierarchy:

• ArtboardWithUniqueName -> ButtonWithUniqueName

The path is then: ArtboardWithUniqueName/ButtonWithUniqueName

Be sure to mark the components and text runs as exported.

Export component name

Do not use ”/” in the name for your components, as that will break the search functionality at runtime.

Semantics for Accessibility

We recommend using Data Binding instead as you’ll be able to do a two way text binding.

As Rive Text does not make use of the underlying platform text APIs, additional steps need to be taken to ensure it can be read by screen readers.

Please see the respective platform/SDKs developer documentation for additional information regarding accessibility concerns.