I have a situation where I have a bunch of Rad Controls (RadTextbox, RadSpinEditor, RadDropDownList) on a User Control. That User Control is then injected into a custom Windows MMC SnapIn. When I do this the TabIndex of the controls is for some reason reversed and the Tab key does not stop on the RadDropDownList anymore. When I use the same User Control inside of a Form or RadForm the TabIndex is as expected and the Tab key stop on the RadDropDownList. I have verified that the TabIndex values are sequential and in the right order and that the TabStop property is True for all the controls.
After some extra digging I found that inside of MMC SnapIn the TabIndex seems to follow the order in which the RadControls are added to the User Control in the Designer code behind file. The TabIndex property is completely ignored.
I am using UI for WinForms 2015 Q3 with C# and Visual Studio 2015.
Is there some bug when RadControls don't have a parent form and are injected into some other parent container?
1 Answer, 1 is accepted
Thank you for writing.
If I understand correctly the DropDownList is hit at some point, but this depends on the controls insert order, not the TabIndex property. Can you test this with the standard .NET controls and see if the TabIndex is respected with them?
In addition, we do not have other reports for similar behavior.
Thank you in advance for your patience and cooperation.
Regards,
Dimitar
Telerik by Progress