We are sorry to hear you had to downgrade, but your point is strong. If the issues related to RadForm are unacceptable for you application, you should better wait until we confirm we have managed to resolve them.
We have already suggested you to try ShapedForm and RadTitleBar instead of RadForm, which would resolve the redrawing issues. Did you try this approach? Please let us know if you have any feedback on this scenario.
As it comes to the performance issues, we will be very to glad if you can elaborate a bit more, on the exact problems you have noticed. This will help us to further optimize our tools.
Generally, the flexibility and the unique visual appearance of our controls are based on an especially designed UI architecture which enables our customers to apply a wide range of customizations when using our product. This architecture performs different initializations, such as property registrations, image processing and themes loading which, of course, leads to some performance penalties, but does not affect the overall user experience. This additional logic is not supported by the Standard Windows Forms Controls and thus they do not provide such great extensibility options. Moreover, the Standard Windows Forms Controls are Win32 controls and they are initially loaded when the Operating System starts. Thus, their performance is favored by the Operating System, which is not the case with RadControls for WinForms. I want to assure you that we have always tried to avoid this tradeoff of performance penalties versus visuals and expanded capabilities.
As you already know, we have all the issues in our todo list and your report is valuable to us since this helps for better issue priority management. We have already resolved some of the issues related to RadForm, as it comes to MDI environment in Q1. However, other issues are more difficult to resolve and require thorough code changes and tests.
the Telerik team
Check out Telerik Trainer
, the state of the art learning tool for Telerik products.