since I updated my MDI form application to 2009 Q2 event MdiChildActivate does not occure if active MDI child changes.
Has this behavior changed or is it a bug ?
Best regards,
Markus
3 Answers, 1 is accepted
0
Deyan
Telerik team
answered on 13 Jul 2009, 11:28 AM
Hello Markus,
Thanks for contacting us and for the reported issue.
Indeed, this is an undesired behavior of RadForm and it will be addressed in the Service Pack which will be released soon.
However, a possible workaround would be to subscribe to the Activate event of each Mdi Child and use it instead.
I hope this is helpful. I have updated your Telerik points for reporting this issue. Do not hesitate to write back if you need further assistance.
Hello Deyan, thanks for your fast response. I tried the workaround you suggested, but Activated event was not fired as well
Regards,
Markus
0
Deyan
Telerik team
answered on 14 Jul 2009, 01:33 PM
Hello Markus,
Thanks for getting back with me.
Actually, the Activated event is not fired due to the same reason which caused the MdiChildActive not to be fired. In the RadForm there is a heavy handling of the WndProc messages so that we can customize the appearance of the form and in one of the message handlers there was a minor issue which prevented the base .NET Framework classes from firing these events.
However, this issues will be sorted out for the Q2 2009 SP1 which is scheduled for the end of this month.
Do not hesitate to write back if you need further assistance.