Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
editor: setting up the update callbacks for n-slicing
I did some refactoring on image and mesh, where I created a 'deformer' that manages which mesh to show. I also abstracted out the parts in Mesh that deals with rendering specifically, called MeshDrawable. There's also a simple UI gated behind a feature flag that shows the N Slicing panel, where you can create, delete, update axis data (hold alt to show the remove axis button). The behavior is that when you create a mesh, the nslicer is deleted and vice versa. I mostly tested this manually. I added a print in the temp mesh's update, and made sure that when any axis gets deleted or updated, the print would trigger. I could add an auto test?! I need to look into that, but wanted to send this out to get some feedback on the approach. Next up: I'll add the algorithm for actually updating the render buffers in the temp mesh. doc: https://www.notion.so/rive-app/9-Slice-Tech-Proposal-Image-only-50b25ea8e79c4efabb681110e288f064#15f3a49ce3534baeafc31c37fb30cc0b Diffs= f99c93181 editor: setting up the update callbacks for n-slicing (#7869) Co-authored-by: Susan Wang <[email protected]>
- Loading branch information