I have synthesized this problem to a very simple example, but I am seeing this same problem everywhere when using my base subclass of an SF Textbox and a standard SF RadioButtonGroup control on the same form.  Here is the complete C# class definition for MyBaseTextbox:

using System;

using System.Collections.Generic;

using System.Text;

namespace RadioButtonGroupProblem

{

public class MyBaseTextbox : MicroFour.StrataFrame.UI.Windows.Forms.Textbox

{}

}

To duplicate the problem, just create an SF StandardForm and drop an instance of MyBaseTextbox on the form.  You don't even need to bind anything to the textbox or configure it any way.  Then drop an instance of a standard SF RadioButtonGroup control on the form.  Again no binding is necessary.  Notice the property named RadioButtonCount on the RadioButtonGroup control defaults to 2.  Now build the solution and notice that the RadioButtonCount has changed to 4.  And from then on, attempting to change the Text property of either of the 2 visible radio buttons gets all mixed up.

This problem seems to happen on various types of forms and with or without binding to data etc.  This sample is just to simplify testing.  My real application requires that I create my own base subclasses of most of the controls but this problem prohibits using them with a RadioButtonGroup control.

Sam Tenney

Glad it is not just me. I am glad this has resurfaced again. 

Don't use the radio group.  This control will be deprecated in future releases as it isn't necessary.  Just use a radio button.  You can have as many "radio groups" as you like on a single form.  Just place each "group" of radio buttons in a container (i.e. panel, ThemedPanel, ThemedGroupBox, etc) and those radio buttons will act as unto themselves as a group or collection.  The RadioGroup that comes with SF has been left for those that have used it, but in the long-term, will be removed from the control collection as it is not necessary.

Thanks Trent, I will give that a try.

Sam Tenney