This is amazing!!! Is there any event handler to to detect onPointsChange, or some trick to do it? For example with the tutorial we detect the input changes of our HDA, but what if we merge attributes in an upstream node without changing the inputs of our HDA, how could we detect that change and update the UI accordingly ? Thanks for the tutorial is superb 🙉
Wonderful tutorial on a subject that I couldn't find covered anywhere else. Thanks a tonne! I hope the monkey is a feature in your other videos. Everything was clearly explained, your pronunciation and diction was very clear, and the video was easy to follow. I'm saving this for future reference!
Phenomenal teaching and guidance through the process! The way you explain each step and the visual guide is very helpful for me to understand the logic behind the process. I hope you get the opportunity to share more informative tutorials like this on other Python operations in Houdini, such as Python viewer states. In any case, thank you, and keep up the good work!
by end, i would say, its so perfect, no need to improve, its working as is after 4 years :). i have a small question though. just like in Pyro Source Node node. i have a list(attributes), with + - buttons to add / remove items in list (density,temp,burn,fuel) etc... where each item has data structure...how to add this feature. any psudo steps will help, thanks again.
Heya! Thanks for the nice words. To do the thing you are asking for, you add a folder in the HDA parameters and change it to Multiparm Block List. Any parameter you put under the folder would be your data struture when you press the + - button.
Really awesome tutorial! One tiny tip... did you know you can hit Ctrl+e in the python editor in houdini to spawn a text editor? Then you don't have to copy/paste.
Hi Sean, thank you for your kind words. Yes. I think it is Alt+E on my keyboard. But I was using the external text editor just because I can zoom in so I can show the code better. Nevertheless that is a good tip. Thank you for sharing too.
very interesting approach. I guess that a way to autopopulate it at every geo change, without the need of buttons, would be to use a python sop inside the digital asset and run from there these functions you have shown (targeting the parent hda node)
Thank you and yes you are correct! Using a python sop inside the digital asset can do the same functionality :D. Both methods could autopopulate it at every geo change without the need of buttons (as you can see at the end of the video). But ultimately it depends on how you want the tool to work and how you want to structure the code :D. The advantage of doing it inside the HDA using the script options is that there are lots of build in event handlers for you to give you finer control. :)
![[TALK] Python Scripting - Houdini](http://i.ytimg.com/vi/CxoVzsxiruY/mqdefault.jpg)
This is amazing!!!
Is there any event handler to to detect onPointsChange, or some trick to do it?
For example with the tutorial we detect the input changes of our HDA, but what if we merge attributes in an upstream node without changing the inputs of our HDA, how could we detect that change and update the UI accordingly ?
Thanks for the tutorial is superb 🙉
Wonderful tutorial on a subject that I couldn't find covered anywhere else. Thanks a tonne! I hope the monkey is a feature in your other videos.
Everything was clearly explained, your pronunciation and diction was very clear, and the video was easy to follow. I'm saving this for future reference!
I'd love to share this video on my blog, if you are willing for me to share a link to the youtube video?
@@CupMcCakers Hi Thank you very much for your comments. Appreciate it. Yes go ahead to share the link to the video. :) Cheers and take care!
Phenomenal teaching and guidance through the process! The way you explain each step and the visual guide is very helpful for me to understand the logic behind the process. I hope you get the opportunity to share more informative tutorials like this on other Python operations in Houdini, such as Python viewer states. In any case, thank you, and keep up the good work!
Thank you very much for the comments! Glad that it has been useful!
thanks a lot!
by end, i would say, its so perfect, no need to improve, its working as is after 4 years :). i have a small question though.
just like in Pyro Source Node node. i have a list(attributes), with + - buttons to add / remove items in list (density,temp,burn,fuel) etc... where each item has data structure...how to add this feature. any psudo steps will help, thanks again.
Heya! Thanks for the nice words. To do the thing you are asking for, you add a folder in the HDA parameters and change it to Multiparm Block List. Any parameter you put under the folder would be your data struture when you press the + - button.
Thank you this was very informative.
I liked the little monkey animations as well :)
Thank you for the kind words
very nice tuts!!!
please make more videos on this
i love near ending monkey story. damn...... thanks for explanation
Thank you, great tutorial, you helped me a lot to figure out the basic of python integration in an hda
Thank you very much for the words, I am glad it has been helpful.
Really awesome tutorial! One tiny tip... did you know you can hit Ctrl+e in the python editor in houdini to spawn a text editor? Then you don't have to copy/paste.
Hi Sean, thank you for your kind words. Yes. I think it is Alt+E on my keyboard. But I was using the external text editor just because I can zoom in so I can show the code better. Nevertheless that is a good tip. Thank you for sharing too.
very interesting approach. I guess that a way to autopopulate it at every geo change, without the need of buttons, would be to use a python sop inside the digital asset and run from there these functions you have shown (targeting the parent hda node)
Thank you and yes you are correct! Using a python sop inside the digital asset can do the same functionality :D.
Both methods could autopopulate it at every geo change without the need of buttons (as you can see at the end of the video).
But ultimately it depends on how you want the tool to work and how you want to structure the code :D.
The advantage of doing it inside the HDA using the script options is that there are lots of build in event handlers for you to give you finer control. :)
This is really great, but I wish you had a hip file for me to dig through like this to experiment with.
Thank you for your feedback. I'll definitely keep that in mind! :)