Greg Cotten
Greg Cotten
> Quite a few plug-ins have needed things like this over the years, but it's usually done with a visible seed parameter that's initialised to a random number. The reason...
> Quite a few plug-ins have needed things like this over the years, but it's usually done with a visible seed parameter that's initialised to a random number. The reason...
I think Resolve may be the only one to unofficially support setting a param during instance creation. It's not a perfect solution though, since I don't want the RNG seed...
Would adding an integer ID to clips make sense? Or even explicitly calling it a RNG seed or something? Could also be useful if you have written multiple plugins to...
closing this in favor of a broader fix: https://github.com/AcademySoftwareFoundation/openfx/issues/203
Could also use @TaskLocal to do something like `Task.resetTimeout()` instead of passing a closure?
> But that timeout object should be `~Escapable` which won't be available until Swift 6.2. Maybe we could make the function that exposes the timeout to be public allowing users...
@swhitty, yea that looks really good!
I'm not super familiar with Swift Macros yet (this is the first one I've really looked at). In the Swift guide they don't seem to use `StaticString` as the argument...
I'll change it to `StaticString` for now - can always be changed back if we figure out how to do string interpolation.