Howdy,
Is it an acceptable strategy for a child object in a typical parent-child OO relationship to raise an event that the parent catches then passes a value back to the child through the EventArgs?
I have a situation where the child needs data from the parent, but the parent does not have that data at the time the child is instantiated so I can not pass it though a constructor.
Thank you,
Keith