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

TOC format documentation is not consistent with decoder impl #376

Open
LiamMartens opened this issue Aug 4, 2024 · 0 comments
Open

TOC format documentation is not consistent with decoder impl #376

LiamMartens opened this issue Aug 4, 2024 · 0 comments

Comments

@LiamMartens
Copy link

In the Rive format docs it explains the following:
Following the properties is a bit array which is composed of the read property count / 4 bytes. Every property gets 2 bits to define which backing type deserializer can be used to read past it.

However as per the Cpp impl and from what I could tell from actually decoding the RIV files; for every 4 properties a whole u32 appears to be allocated - which the explanation doesn't mention. Should be updated for clarity for anyone trying to work with the format.

https://help.rive.app/runtimes/advanced_topics/format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant