I had a feeling there was more there but the reason i didn't bother exploring it more was because of the lifecycle. From my experiments the child functions are always executed first and the parent's ExecutePageHierarchy() always executes after. I could never hook into a parent's event to add anything.
In my example i had a FunctionParent and FuctionChild and i believe this mimics the idea of the "whole page-content" being inside a function.
I was looking at a different part of your form builder code earlier today where i saw you had extended the FCC but i'll dig into the links you provided to see how you're able to execute code in the parent function before the child function is called.
In my example i had a FunctionParent and FuctionChild and i believe this mimics the idea of the "whole page-content" being inside a function.
I was looking at a different part of your form builder code earlier today where i saw you had extended the FCC but i'll dig into the links you provided to see how you're able to execute code in the parent function before the child function is called.