I really need some level of control over which inputs trigger a preview. When any update to any input causes a preview it's near impossible to provide the user any textual feedback without firing at least 2 preview generations.
There was a recent change in the Fusion API (some time in May maybe?) which is now resulting in updates of READ ONLY fields causing a preview to be triggered. This "broke" my Helical Gear generator add-in by causing an infinite preview loop - a preview updates a textbox input to provide the user with detailed information about the generated gear, writing to this input was triggering another preview, and so on. I've put a band-aid on the problem in v1.0.2 which drops the preview looping down from infinite to probability 2 to 4 preview generations (I have no way to provide myself with feedback about how many previews happen because that would cause previews to triggered and message boxes are more than annoying for this) but it's not a solution.
For some reason the "Group" control has always triggered a preview when expanding or collapsing which is a bit crazy IMO.
I see three solutions off the top of my head which could all co-exist but I'd welcome any one of them
1) give each input a boolean property along the lines of "TriggersPreviewOnChange"
2) allow the onchanged handler the ability to prevent a preview
3) within the preview function give the ability to abort the generation of a new preview - aka use previous preview result
Fusion
