Unfortunately you didn't reproduce anything even close to the described scenario.
I have wrapped the Syncfusion edit into a custom control, you should first have to do that. Then I hosted this control on a winform in the same control library. Then I created another custom control (non-visual) in the same control library that can instantiate an instance of this winform. I exposed COM interfaces to this set of controls.
To replicate this problem, you should do that. Then I called that COM interface from an MFC application, using the created TLB file and using the IID's of the methods to invoke the instance of this form object via the non-graphical control. You can't directly invoke the graphical control in MFC unless you embed it on the MFC dialog, which I didn't want to do - so that was why I did it this way.
Please let me know if you can get me a fix for this bug after you reproduce it. Also, we can set up a webex so I can show it to you if you want.
It may be an artifact of the MFC event loop so there may be a more general .NET way around this, I haven't yet had time to look into this.
>Hi dunion,
Our apologies for the delayed response. I have tested for this issue using a sample and was not able to see the problem. This is how I went about testing this issue :
1.Run the attached sample.
2.Click EditControl.
3.EditControl is displayed in a window.
4.Press Delete.
5.The delete is not posted to the containing application.
Please let me know if I am missing something.
Thanks for your patience.
Regards,
Ebenezer.P
sample
