There's a few techniques. What I do is to make an array (or cluster if
they're not identical in appearance) of switches and periodically compare
the array with a cached copy. If it has changed, then I find the new button,
set all the others "off" and write the new array value back to the control
via a local. If two buttons have been pressed since the last poll, all
buttons are switched off.
Another way I've never done is to customise a slider control so it looks
like the slider is an "on" button against a background of "off" buttons.
Clicking on one of the "off" buttons moves the slider over it, making it
look as if it has switched on while the previous one switches off. This is a
bit tedious to do and it's not very flexible, but if you're happy with it it
ce
rtainly simplifies the code.
An alternative and simple change to your existing application would be to
set the switch "false" using a local after the function it carries out has
completed executing, but this means you can't catch an intermediate
selection change.
frank wrote in message
news:bb3c5523.0111150709.405a346f@posting.google.com...
> I am currently writing an application that requires the selection of
> one of four switches used to drive an index head to a specific
> position. The switches are set up as a cluster of four. When the index
> head reaches the desired position, optical switches are activated
> which removes the drive signal and activates a brake to hold the
> current position. The operator then performs whatever test he must and