Steve Alexander wrote:
You could have a flag in DataSkin instances called _has_been_added. It
is initially cleared. It gets set when manage_afterAdd is called on it.
The DataSkin sends an _objectChanging event only if the _has_been_added
flag is set.
Of course, the name of the attribute
It could cause a problem if the object is added after any other sort of
change from the point of view of the Agent. The Agent would view it as
having been added, when in fact it is actually merely changed. I have not,
however, been able to think of any scenario where this condition could
occur
I have a GenericTrigger in a Folder with Customizer support.
When I set it to trigger upon Add, my method doesn't get triggered when
I add a new DataSkin-derived-ZClass instance. However, when I set it to
trigger on Change, my method gets called on adding a new DataSkin.
I can't see anything
