TouchDesigner with States!

[@canrachmakeit]

You are so helpful to me. Thank you for creating this. I’ve been tryna wrap my head around this very concept!

[@davidzwitser]

Awesome to hear!

[@TS-or4lz]

Great tool thank you very much for sharing this. I was wondering if someone had build something like this after having a very long chain of timers that triggered each other and completly losing sight what actually triggers what :D

[@tekt0]

That error with the unknown path is caused by having the parameter style be "OP" (or "COMP", etc). For parameters that can take more than one operator, you can use the style "Str" and then call the `foo.par.Things.evalOPs()` to resolve the string to a list of operators.

[@davidzwitser]

Aah, evalOPs is a good one! Thanks for the other suggestion aswel. The reason I didn't make it type Str is because then connecting with dropping one onto the other doesn't work anymore. @Unveil suggested to use a messageBox, which would also make the possibility to not overwrite the old connection. For now I don't think that benefit outweighs the problem though; namely it conflicts with my design goal of keeping it as minimal and native to TouchDesigner as possible. But I am still testing with that.

[@AlphaMoonbase]

Sweet stuff! Happy to see more creators utilizing the Olib :)

[@puck_nz]

Top Job ! I'm enjoying having a play with it ... any chance you'd be up for sharing some example COMPs to fast understanding the implementation ?

[@davidzwitser]

Thanks! That's great to hear :). And good one, I'll make an examples pack!

[@davidzwitser]

olib.amb-service.net/component/state-circuit-snippets Here is the snippet pack! :)

[@FunctionStore]

this is amazing, thanks for sharing!

[@FunctionStore]

Have you considered uploading it to the olib as well? Would be a great addition to the utility tools there!

[@davidzwitser]

@@FunctionStore Good one! I'm going to look into that

[@davidzwitser]

@@FunctionStore It is on there :) olib.amb-service.net/component/state-circuits

[@FunctionStore]

@@davidzwitser lovely cheers! ☺️

[@unveil7762]

Really well done!!! For the warning you can maybe just use a string parameter… and check for the name of the operator and pass it if they have the state tag. Should work. Than to make the connections you can start to use the messageBox with some buttons, is a function in tdu or tdf, and for the parameters you can start to write some infos so each parameter when the mouse is over give a little description. I think the system is pretty cool… and your networks are really clean and interactives!! ❤🎉😊ps: you know me i am Simo from berlin we meet at the Td meet up

[@davidzwitser]

Ooh hey Simo! I didn't know it was you 😁. Thanks for the feedback and compliments! I didn't know ui.messageBox and not even the TDF library, cool! I'll try out your suggestion 😁, it might indeed streamline the connecting of multiple State or Condition COMPs to one. And the infos are written! :)

[@davidzwitser]

Link to the Toolkit: olib.amb-service.net/component/state-circuits Link to Snippets Pack to get started: olib.amb-service.net/component/state-circuit-snippets