Moritz Mœller

> I wrapped the drawbot using the suite + item approach and it turned out quite nice Indeed! Looks juicy. I think we don't have to mirror stuff like `AEGP_CameraType_NUM_TYPES`....

> I assume acquiring and releasing suites is very cheap (like just adding a reference), but I don't know that for sure. Do you happen to know if acquiring and...

Hey @AdrianEddy, isn't this in a state where it would warrant a merge and release? Even if it's not perfect (docs etc.)?

Thank you so much for this and yeah, no time to review for now. Everything I saw looked awesome and well though-out. I'm working full time on an in-house node-based...

Everything is published on `crates.io`. I could not even test any builds as I'm on a Linux box. So kringers fossed. TODO: make the `docs.rs` build succeed. I will open...

> Also, isn't sequence data always flattened and restored per thread? I mean that the calls done by AE from different threads don't actually use the same pointer, but rather...

This looks awesome. I especially like the closure stuff. So very Rust. Regarding naming: two things. I think I used `set_*()` a lot (because I was Rust n00b) but most...

> This does make sense, but I didn't find this behavior documented anywhere Welcome to the Ae SDK docs. ;)

I believe to recall that the idea was that you can use other ways to sync plug-in state with widgets. Or go through `sequence_data`. But I have to look at...

Nope. I have a custom-built Ae curve widget somewhere that is 100% Rust. I.e. something that looks and feels like the one in the Ae Curves filter. Screenshot is in...