endSave in outputprocessor

   2103   2   1
User Avatar
Member
3 posts
Joined: Dec. 2015
Offline
I found endSave call is removed in H19.5. Any plan to add it back or is there an alternative method to use?

A simple usage is, we are collecting information during Houdini saving out usd files and generate a log.
User Avatar
Staff
4574 posts
Joined: July 2005
Offline
In 19.5 a new instance of your output processor object is created for each save operation, and destroyed at the end of the save. This (we thought) made the endSave call unnecessary. But I suppose the lack of proper dewstructor methods in Python means there are still use cases for this method (or something equivalent)? Please submit an RFE to request the re-introduction of this method if you need it (though an alternative approach in your case might be to write the log as you go, and rely on the destruction of the output processor object to destroy/close the log file object). Thanks!
User Avatar
Member
3 posts
Joined: Dec. 2015
Offline
Thank you Mark!
I wasn't aware a new instance of the output processor object is created for each save operation (v.s. 19.0 only one instance is created). Implementing a __del__() method in the output processor to serve as the endSave() works for us!

Wayne
  • Quick Links