>This probably won't help much, but your question got me to look at the framework code and I noticed what (might) be an opportunity for refactoring code (and making it a bit more generic). Currently, there is code in the framework for propagating some types of messages between parents and children. The code all looks surprisingly similar:
>

Hmm...this sounded familiar so I did a search - this is very similar to the suggestion I made for abstracting out pseudo-event messages (eg. ThisForm.SetAll("cEvent", "MyEvent") ). Maybe the solution could incorporate both suggestions (plus handle return values - mine doesn't).