Is there a limit on # of radio buttons

[=?Utf-8?B?UGFycm90?=]

I have 8 radio buttons on my Windows form but I can only select up to the
first 4. If I click on any button beyond the 4th one and then come back into
the program again the 4th button is always checked instead of the 5th or 6th
etc. I followed the logic thru the debugger and can see where the 5th button
is progammatically checked but the window shows the 4th checked instead.
Does anyone have a clue as to what's going on here? All of the radio buttons
are in a group box.
Dave

[=?UTF-8?B?R8O2cmFuIEFuZGVyc3Nvbg==?=]

Parrot wrote:

I have 8 radio buttons on my Windows form but I can only select up to the
first 4. If I click on any button beyond the 4th one and then come back into
the program again the 4th button is always checked instead of the 5th or 6th
etc. I followed the logic thru the debugger and can see where the 5th button
is progammatically checked but the window shows the 4th checked instead.
Does anyone have a clue as to what's going on here? All of the radio buttons
are in a group box.
Dave

If there is a limit, it's certainly not four. Rather something like
65536 or 4294967296.

Where are you storing the data? Have you checked if the stored value is
correct or not?

How do you make the right radio button selected when you load the data?

--
Göran Andersson
_____
http://www.guffa.com

[=?Utf-8?B?UGFycm90?=]

The logic I am using is very simple. When loading the program I check a
passed variable. The code goes like this:

if(dateformat.C ompare("month") ==0)
{
radioButton5.Ch ecked = true;
}

However, when the window is displayed, it shows radioButton4 checked
instead. I followed the logic in debug mode and that is the only radiobutton
programmaticall y checked. I don't understand how something so simple cannot
work.
Dave

"Göran Andersson" wrote:

Parrot wrote:

I have 8 radio buttons on my Windows form but I can only select up to the
first 4. If I click on any button beyond the 4th one and then come back into
the program again the 4th button is always checked instead of the 5th or 6th
etc. I followed the logic thru the debugger and can see where the 5th button
is progammatically checked but the window shows the 4th checked instead.
Does anyone have a clue as to what's going on here? All of the radio buttons
are in a group box.
Dave

If there is a limit, it's certainly not four. Rather something like
65536 or 4294967296.

Where are you storing the data? Have you checked if the stored value is
correct or not?

How do you make the right radio button selected when you load the data?

--
Göran Andersson
_____
http://www.guffa.com

[Ken Halter]

"Parrot" <Pa****@discuss ions.microsoft. comwrote in message
news:AA******** *************** ***********@mic rosoft.com...

>
However, when the window is displayed, it shows radioButton4 checked
instead. I followed the logic in debug mode and that is the only
radiobutton
programmaticall y checked. I don't understand how something so simple
cannot
work.
Dave

VB6 dev here, so dotNet Radio buttons may've changed (but I doubt it, since
they were the same in VB3/NT3.51 as they are in VB6/XP).. They're not as
easy to work with as they seem.

Since they change to "True" when they get focus, no matter what, you have to
make sure of a few things before hiding/showing/disabling/enabling them. The
simplest method I've seen (and used extensively) is to disable their
container until focus is where you'd like it to be.

For example... if Button3's currently = True, but when your form shows (or
you're enabling/disabling controls), the first control that gains focus is
Button5, Button5 will be set = True, no matter what. So, disabling the
container forces focus elsewhere, which prevents this problem... since my
apps control hardware and are used in the cleanroom, we don't allow focus to
"stick" to a control that may cause something to move... too many people can
walk up and lean on the keyboard, etc.... so, I usually drop a picturebox on
the form, set its background = form's background and set focus to that.
Since the picturebox doesn't show a focus rectangle, and there's no code in
its click event, people can lean on the keyboard all they want without
worry.

In your case, maybe you have a textbox or command button to set focus to,
instead.... what ever the case, you'll probably find your "rouge radio
button" that keeps setting itself = true is getting focus without your
involvement..

[=?Utf-8?B?UGFycm90?=]

This is really crazy. The only way I can keep radiobutton4 from being
checked even though radiobutton5 is checked is to disable radiobutton4.
However, then if radiobutton6 is checked then the check mark goes to
radiobutton5, the one above it. If I disable radiobutton5 when checking
radiobutton6 the check mark will go back to radiobutton4. I removed and
re-added the radiobuttons but to no avail. I still get the same problem.
Simply put. the system will not properly handle beyond 3 radio buttons in the
same group. Such a simple program and I am spinning my wheels. It couldn't
be a bug could it?
Dave

"Ken Halter" wrote:

"Parrot" <Pa****@discuss ions.microsoft. comwrote in message
news:AA******** *************** ***********@mic rosoft.com...

However, when the window is displayed, it shows radioButton4 checked
instead. I followed the logic in debug mode and that is the only
radiobutton
programmaticall y checked. I don't understand how something so simple
cannot
work.
Dave

VB6 dev here, so dotNet Radio buttons may've changed (but I doubt it, since
they were the same in VB3/NT3.51 as they are in VB6/XP).. They're not as
easy to work with as they seem.

Since they change to "True" when they get focus, no matter what, you have to
make sure of a few things before hiding/showing/disabling/enabling them. The
simplest method I've seen (and used extensively) is to disable their
container until focus is where you'd like it to be.

For example... if Button3's currently = True, but when your form shows (or
you're enabling/disabling controls), the first control that gains focus is
Button5, Button5 will be set = True, no matter what. So, disabling the
container forces focus elsewhere, which prevents this problem... since my
apps control hardware and are used in the cleanroom, we don't allow focus to
"stick" to a control that may cause something to move... too many people can
walk up and lean on the keyboard, etc.... so, I usually drop a picturebox on
the form, set its background = form's background and set focus to that.
Since the picturebox doesn't show a focus rectangle, and there's no code in
its click event, people can lean on the keyboard all they want without
worry.

In your case, maybe you have a textbox or command button to set focus to,
instead.... what ever the case, you'll probably find your "rouge radio
button" that keeps setting itself = true is getting focus without your
involvement..

[Peter Duniho]

On Thu, 17 Jul 2008 18:26:02 -0700, Parrot
<Pa****@discuss ions.microsoft. comwrote:

[...]
Simply put. the system will not properly handle beyond 3 radio buttons
in the
same group. Such a simple program and I am spinning my wheels. It
couldn't
be a bug could it?

Surely it's a bug. But it's probably in your code.

Unfortunately, you haven't shared that with us. So it's not possible for
us to point it out.

If you can post a concise-but-complete code sample that reliably
reproduces the problem, it should be possible to provide a more complete
answer.

Pete

[=?Utf-8?B?UGFycm90?=]

I am pasting the entire code for the C# program below. As I mentioned
earlier I can follow the logic in debug mode and I can see where radiobutton5
is set to checked but it still shows radiobutton4 with the check when the
window is displayed.

namespace WindowsApplicat ion1
{
public partial class convertdate : Form
{

public string xdateformat;

public convertdate(str ing field, string dateformat)
{
InitializeCompo nent();
label2.Text = field;

xdateformat = dateformat;

if (dateformat.Com pareTo("1") == 0)
radioButton1.Ch ecked = true;
else
if (dateformat.Com pareTo("101") == 0)
{
radioButton2.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("107") == 0)
{
radioButton3.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("year") == 0)
{
radioButton4.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("month") == 0)
{
radioButton5.Ch ecked = true;
radioButton1.Ch ecked = false;

}
else
if (dateformat.Com pareTo("day") == 0)
{
radioButton6.Ch ecked = true;
radioButton1.Ch ecked = false;

}
else
if (dateformat.Com pareTo("monthna me") == 0)
{
radioButton7.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("dayname ") == 0)
{
radioButton8.Ch ecked = true;
radioButton1.Ch ecked = false;
}

}

private void OnCancel(object sender, EventArgs e)
{
this.Close();
}

private void OnOk(object sender, EventArgs e)
{
if (radioButton1.C hecked)
xdateformat = "1";
else
if (radioButton2.C hecked)
xdateformat = "101";
else
if (radioButton3.C hecked)
xdateformat = "107";
else
if (radioButton4.C hecked)
xdateformat = "year";
else
if (radioButton5.C hecked)
xdateformat = "month";
else
if (radioButton6.C hecked)
xdateformat = "day";
else
if (radioButton7.C hecked)
xdateformat = "monthname" ;
else
if (radioButton8.C hecked)
xdateformat = "dayname";
this.Close();
}
}
}

"Peter Duniho" wrote:

On Thu, 17 Jul 2008 18:26:02 -0700, Parrot
<Pa****@discuss ions.microsoft. comwrote:

[...]
Simply put. the system will not properly handle beyond 3 radio buttons
in the
same group. Such a simple program and I am spinning my wheels. It
couldn't
be a bug could it?

Surely it's a bug. But it's probably in your code.

Unfortunately, you haven't shared that with us. So it's not possible for
us to point it out.

If you can post a concise-but-complete code sample that reliably
reproduces the problem, it should be possible to provide a more complete
answer.

Pete

[Peter Duniho]

On Thu, 17 Jul 2008 20:58:02 -0700, Parrot
<Pa****@discuss ions.microsoft. comwrote:

I am pasting the entire code for the C# program below.

That wasn't a complete code sample.

Also, as a minor suggestion for making your code more pleasant for others
to read: when writing "if/else if/else" statements, it's customary to
avoid excessive indentation by writing "else if" on the same line, and
indenting each "else if" and the final "else" the same amount as the
initial "if".

Pete

[Michael D. Ober]

"Parrot" <Pa****@discuss ions.microsoft. comwrote in message
news:26******** *************** ***********@mic rosoft.com...

>I am pasting the entire code for the C# program below. As I mentioned
earlier I can follow the logic in debug mode and I can see where
radiobutton5
is set to checked but it still shows radiobutton4 with the check when the
window is displayed.

namespace WindowsApplicat ion1
{
public partial class convertdate : Form
{

public string xdateformat;

public convertdate(str ing field, string dateformat)
{
InitializeCompo nent();
label2.Text = field;

xdateformat = dateformat;

if (dateformat.Com pareTo("1") == 0)
radioButton1.Ch ecked = true;
else
if (dateformat.Com pareTo("101") == 0)
{
radioButton2.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("107") == 0)
{
radioButton3.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("year") == 0)
{
radioButton4.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("month") == 0)
{
radioButton5.Ch ecked = true;
radioButton1.Ch ecked = false;

}
else
if (dateformat.Com pareTo("day") == 0)
{
radioButton6.Ch ecked = true;
radioButton1.Ch ecked = false;

}
else
if (dateformat.Com pareTo("monthna me") == 0)
{
radioButton7.Ch ecked = true;
radioButton1.Ch ecked = false;
}
else
if (dateformat.Com pareTo("dayname ") ==
0)
{
radioButton8.Ch ecked = true;
radioButton1.Ch ecked = false;
}

}

private void OnCancel(object sender, EventArgs e)
{
this.Close();
}

private void OnOk(object sender, EventArgs e)
{
if (radioButton1.C hecked)
xdateformat = "1";
else
if (radioButton2.C hecked)
xdateformat = "101";
else
if (radioButton3.C hecked)
xdateformat = "107";
else
if (radioButton4.C hecked)
xdateformat = "year";
else
if (radioButton5.C hecked)
xdateformat = "month";
else
if (radioButton6.C hecked)
xdateformat = "day";
else
if (radioButton7.C hecked)
xdateformat = "monthname" ;
else
if (radioButton8.C hecked)
xdateformat = "dayname";
this.Close();
}
}
}

"Peter Duniho" wrote:

>On Thu, 17 Jul 2008 18:26:02 -0700, Parrot
<Pa****@discus sions.microsoft .comwrote:

[...]
Simply put. the system will not properly handle beyond 3 radio buttons
in the
same group. Such a simple program and I am spinning my wheels. It
couldn't
be a bug could it?

Surely it's a bug. But it's probably in your code.

Unfortunatel y, you haven't shared that with us. So it's not possible for
us to point it out.

If you can post a concise-but-complete code sample that reliably
reproduces the problem, it should be possible to provide a more complete
answer.

Pete

We need the code behind the form. That's where the grouping of radio
buttons is controlled. You have a grouping error.

Mike.

[Matt]

On Jul 17, 9:58*pm, Parrot <Par...@discuss ions.microsoft. comwrote:

I am pasting the entire code for the C# program below. *As I mentioned
earlier I can follow the logic in debug mode and I can see where radiobutton5
is set to checked but it still shows radiobutton4 with the check *when the
window is displayed.

There's nothing wrong with your code, specifically, I pasted it into
an application
and it worked fine. The problem is probably in what you do with the
xdateformat
variable after the form closes. Can you show the code that calls this
form?

matt