1. checkbox issue
I've found that an 'onChange()' of a checkbox does not trigger an event
however 'onClick()' does trigger for both 'clicking' the box as well as
'spacebar'ing' the box.
Should 'onChange()' work for the checkbox??
...george
2. Re: checkbox issue
Hi George,
----- Original Message -----
From: "George Walters" <gwalters at sc.rr.com>
To: "EUforum" <EUforum at topica.com>
Subject: checkbox issue
> I've found that an 'onChange()' of a checkbox does not trigger an event
> however 'onClick()' does trigger for both 'clicking' the box as well as
> 'spacebar'ing' the box.
>
> Should 'onChange()' work for the checkbox??
The decision to use Click rather than Change is based on the behaviour of
Visual Basic (I think). Click events tend to be mouse oriented and single
actions, and Change events tend to be keyboard oriented.
-----------
Derek
3. Re: checkbox issue
> Hi George,
> ----- Original Message -----
> From: "George Walters" <gwalters at sc.rr.com>
> To: "EUforum" <EUforum at topica.com>
> Sent: Wednesday, August 22, 2001 10:24 PM
> Subject: checkbox issue
> > I've found that an 'onChange()' of a checkbox does not trigger an event
> > however 'onClick()' does trigger for both 'clicking' the box as well as
> > 'spacebar'ing' the box.
> >
> > Should 'onChange()' work for the checkbox??
>
> The decision to use Click rather than Change is based on the behaviour of
> Visual Basic (I think). Click events tend to be mouse oriented and single
> actions, and Change events tend to be keyboard oriented.
I think what George is saying is, shouldn't 'spacebar' be trapped in
onChange(), as it is not a mouse event?
Makes sense to me..
Chris
4. Re: checkbox issue
Thanks Chris for that clarification.
I guess if it is important to distinguish between SPACEBAR and Mouse
invocations the it would be nice to have two distinct events. However, that
is not a part of the Microsoft GUI principles. It would effect all controls
that currently react to keyboard and mouse - Buttons, Radio, Lists, Combos
etc...
If SPACEBAR (or whatever key) trapping is important, the KeyDown/KeyPress
events are still available.
I'm not currently planning to have onChange fire for SPACEBAR invocations of
Checkboxes. Unless someone can convince me that it is worthwhile.
-----------
cheers,
Derek Parnell
Senior Design Engineer
Global Technology Australasia Ltd
dparnell at glotec.com.au
---------------------
> -----Original Message-----
> From: Derek Parnell [mailto:ddparnell at bigpond.com]
> Sent: Thursday, 23 August 2001 8:49 AM
> To: Derek at Work
> Subject: Fwd: Re: checkbox issue
>
>
>
>
> ------- Start of forwarded message -------
> From: Chris Bensler <bensler at telus.net>
> To: EUforum <EUforum at topica.com>
> Reply-To: EUforum at topica.com
> Subject: Re: checkbox issue
> Date: 23/08/2001 7:14:40 AM
>
>
> > Hi George,
> > ----- Original Message -----
> > From: "George Walters"
> <gwalters at sc.rr.com>
> > To: "EUforum" <EUforum at topica.com>
> > Sent: Wednesday, August 22, 2001 10:24
> PM
> > Subject: checkbox issue
> > > I've found that an 'onChange()' of a
> checkbox does not trigger an event
> > > however 'onClick()' does trigger for
> both 'clicking' the box as well as
> > > 'spacebar'ing' the box.
> > >
> > > Should 'onChange()' work for the
> checkbox??
> >
> > The decision to use Click rather than
> Change is based on the behaviour of
> > Visual Basic (I think). Click events
> tend to be mouse oriented and single
> > actions, and Change events tend to be
> keyboard oriented.
>
> I think what George is saying is,
> shouldn't 'spacebar' be trapped in
> onChange(), as it is not a mouse event?
> Makes sense to me..
>
> Chris
>
> ddparnell at bigpond.com
>
> er
>
>
>
>
> -------- End of forwarded message --------
>
>
>
confidential information intended solely for the use of the individual or
entity to whom they are addressed. If you are not the intended recipient of
this message you are hereby notified that any use, dissemination,
distribution or reproduction of this message is prohibited. If you have
received this message in error please notify the sender immediately. Any
views expressed in this message are those of the individual sender and may
not necessarily reflect the views of Global Technology Australasia Limited.
