| Subject |
Re: pushbutton |
| From |
edward racht <e.racht@gmail.com> |
| Date |
Mon, 8 Mar 2021 08:07:18 -0500 |
| Newsgroups |
dbase.getting-started |
On 3/8/2021 5:52 AM, Andy Taylor wrote:
> The issue with radio buttons is that they work in groups.
>
> If the designer puts his code that reacts to a change in settings in the onChange method then he needs to be prepared
> to code for that method being fired twice. Why? Because the radioButton gaining selection will fire it and so will the
> radioButton that loses it.
>
> Using the onLeftMouseUp event is an effective way of avoiding the problem noted above and not having to wrap your
> head around the extra bit of code that would be required, which, very simplified is as follows:
> radioButton::onChange
> If my setting is true
> do this
> else
> do nothing
> return
Andy,
Your explanation does help. Thank you for your expertise.
I have found the pushbutton timer discussion a learning situation.
ed
|
|