Adam Gerhant

I just ran into a very similar issue when running async code with futures_lite::future::block_on in a web worker. The web worker would close before a promise could resolve. I think...

I tried with v0.3.0 and found that the close() function has to be removed, and spawn_local has to be used instead of block_on. If the close() is not removed then...

I added a spawn_async method that spawns the future with spawn_local, and uses a static arc flag that is updated when the function is complete and then used to close...

I think this is because I forgot to migrate the brush tool to using the message buffering and using the transform of its own layer, as returned from the render...

Why is the Footprint transform used instead of using the current document_to_viewport transform? Instead of `.map(|(footprint, transform)| footprint.transform * transform)`, `.map(|(_, transform)| self.document_to_viewport * transform)` can be used, which seems...

This would solve #1919

This is implemented in `impl crate::vector::ConcatElement for super::VectorData` and `pub fn vector_new_ids_from_hash`. The Flatten Vector Elements node uses `.concat`, where the vector data ids are generated from the hash of...