I have a simpleObject plugin with a bunch of parameters stored in a regular parameter block. The plugin is designed to be referenced by other plugins within max (it’s a type of object that pflow particles are meant to be distributed on).
Is there a way to tell its parameter block NOT to fire NotifyDependents messages when certain pblock entires are changed? For example, there’s a checkbox that allows you to enable/disable the visibility of its viewport icon. I don’t want pflow to recalculate all of its particle data when that checkbox is toggled, because that setting has no impact on the resulting particles…so it would be nice to be able to tell max not to fire off messages when that checkbox is changed. Currently it seems those messages are fired whenever any pblock entry is changed.
I know you can call EnableNotifications(FALSE) on the pblock before calling SetValue(…), but I can’t do that when max internally calls SetValue after user input on the UI controls…
Or alternatively, can I tell max which messages to fire? For example, it would be nice to tell the icon toggle to only fire off PART_DISPLAY or whatever, instead of PART_ALL, when clicked.
Only one plugin is mine. My plugin generates geometry that I’m using to scatter particles over with particle flow. If I made both plugins I could probably track the messages sent between them…the problem lies in the fact that particle flow resets the sim when any pblock change messages are sent.
you can hash all critical for your plugin parameter values on build object and before next build check the hash value first. if the hash value is different than on previous build do a new build.