Any way to make a CheckBoxList behave like a RadioButton?

[MattB]

I have a CheckBoxList that under some circumstances I want to only allow
one selection, so that if you select a different item, whatever was
selected before becomes un-selected.
Any ideas on how to do this?

Ideas, and even better, examples would be appreciated!

Matt

[Collin Chung]

Hi Matt,

I'd use a javascript to do this, but it only works when the
RepeatLayout property is set to Flow.

On mouse-click, it resets all checkboxes in the list to unchecked, and
then checks the current item.

Here's how the CheckBoxList control should look like:

<asp:CheckBoxLi st id="CheckBoxLis t1" runat="server" RepeatLayout="F low"
onclick="try{if (event.srcEleme nt.type=='check box'){var
nodes=event.src Element.parentN ode.childNodes; for(i=0,numberO fElements=child Nodes.length;i< numberOfElement s;++i)if(childN odes[i].type=='checkbo x')childNodes[i].checked='';}ev ent.srcElement. checked='checke d';}catch(E){}" >

Alternatively, you could consider using the RadioButtonList .

[MattB]

Collin Chung wrote:

Hi Matt,

I'd use a javascript to do this, but it only works when the
RepeatLayout property is set to Flow.

On mouse-click, it resets all checkboxes in the list to unchecked, and
then checks the current item.

Here's how the CheckBoxList control should look like:

<asp:CheckBoxLi st id="CheckBoxLis t1" runat="server" RepeatLayout="F low"
onclick="try{if (event.srcEleme nt.type=='check box'){var
nodes=event.src Element.parentN ode.childNodes; for(i=0,numberO fElements=child Nodes.length;i< numberOfElement s;++i)if(childN odes[i].type=='checkbo x')childNodes[i].checked='';}ev ent.srcElement. checked='checke d';}catch(E){}" >

Alternatively, you could consider using the RadioButtonList .

Thanks. I'll give it a shot.
I want to use the CheckBoxList instead of a RadioButtonList because in
many cases the user is allowed to make multiple selections. I thought
that keeping one kind of control and changing the behavior would be a
more consistent interface.

Matt

[Alan Silver]

>I want to use the CheckBoxList instead of a RadioButtonList because in

many cases the user is allowed to make multiple selections. I thought
that keeping one kind of control and changing the behavior would be a
more consistent interface.

Actually, you will confuse the user far more by doing this than you
would if you changed the controls to radio buttons.

User subconsciously expect things to work a certain way, and if you try
and change the behaviour of standard elements, you will confuse users.
At the least, this will cause them to have to stop and think when trying
to use your site, at worst, you will confuse them enough that they will
give up and go elsewhere.

Don't underestimate this point, it is a very strong one that most people
miss. If you sit and watch non-web designers trying to use most web
sites that exist, you will be amazed at how much they struggle with poor
design choices like this.

See www.useit.com for the opinions of the web's #1 guru on usability
issues. He speaks a lot about the dangers of changing expected
behaviour.

HTH

--
Alan Silver
(anything added below this line is nothing to do with me)

[MattB]

Alan Silver wrote:

I want to use the CheckBoxList instead of a RadioButtonList because in
many cases the user is allowed to make multiple selections. I thought
that keeping one kind of control and changing the behavior would be a
more consistent interface.

Actually, you will confuse the user far more by doing this than you
would if you changed the controls to radio buttons.

User subconsciously expect things to work a certain way, and if you try
and change the behaviour of standard elements, you will confuse users.
At the least, this will cause them to have to stop and think when trying
to use your site, at worst, you will confuse them enough that they will
give up and go elsewhere.

Don't underestimate this point, it is a very strong one that most people
miss. If you sit and watch non-web designers trying to use most web
sites that exist, you will be amazed at how much they struggle with poor
design choices like this.

See www.useit.com for the opinions of the web's #1 guru on usability
issues. He speaks a lot about the dangers of changing expected behaviour.

HTH

Well I decided against it before seeing your reply, but this affirms my
decision.

Thanks for the input!

Matt