Inheritance Issue with SplitContainers SplitPanels

[Mark]

I originally posted this in the wrong forum, so that one can be delete.

I am having an issue with SplitPanels that are added into a RadSplitContainer when those controls are inherited.  I have a base form class that has a RadSplitContainer on it, with two SplitPanels in it.  Then I create the new form based on that base form.  I can open the designer the first time and save, but once I close it and re-open it, I get "Duplicate component name 'splitPanel1'. Component names must be unique and case-insensitive"

Some things I have noticed is that the splitPanel lack the "Modifier" property. 

Any help would be greatly accepted.

Thanks

[Mark]

One thing I did forget to state, is that on the inherited form, in one of the SplitPanel, I added a bunch of rad controls (label, textbox, dropdown, etc).

 

 

[Dess | Tech Support Engineer, Principal]

Hello, Mark,         

Following the provided information, I was able to replicate the problem with the SplitPanels in the inherited form. This is a known issue of Windows Forms design-time in general. Please refer to the following StackOverflow thread: https://stackoverflow.com/questions/22181926/controls-on-inherited-form-are-locked-can-it-be-undone

We also have a known issue regarding the Modifiers property of the SplitPanels.You can track its progress, subscribe for status changes and add your comments on the following link - https://feedback.telerik.com/Project/154/Feedback/Details/199235-fix-radsplitcontainer-the-splitpanel-access-modifier-cannot-be-set-to-public-o

I hope this information helps. If you have any additional questions, please let me know.  

 

Regards,
Dess
Progress Telerik

[Mark]

Dess

Thanks for the reply, I was hoping this wasn't the case.  This throws a huge monkey wrench into our design using SplitContainers/SplitPanels in our base classes.  After reading the Stack Overflow posts, one suggested adding the controls in the constructor.  Not sure how well that will work, but I will give it a try.  

One questions, does the RadPageView have this same issue?  I could use that instead.

 

TIA

[Dess | Tech Support Engineer, Principal]

Hello, Mark,          

When the Modifiers property of a RadControl is set to "protected" or "public" in a base form, the code DOM serialization and the overall design-time behavior of the control is incorrect in the child form. The following Knowledge Base article is quite useful on this topic: https://www.telerik.com/support/kb/winforms/details/using-radcontrols-for-winforms-with-inherited-forms

As to the RadPageView, I have tested the same scenario and when the Modifiers property of the control and the separate pages is set to Protected, everything seems to work as expected on my end. You can give it a try if it suits your requirement.

If you need any further assistance please don't hesitate to contact me.

Regards,
Dess
Progress Telerik