Another possibility is to store the old state in a mouseDown handler
(be sure to discount the hilite of the target). If you're using
1.3Ax, this would be a good situation to use a local declaration in
the group's script rather than a global.
> Have you noticed the behavior of the hilitedButton property under these
> circumstances? In going from a "higher" radio option to a "lower" one,
> the property is updated before your handler is called. When going from
> a "lower" option to a "higher" one, the property isn't updated until after
> your handler is exited.
Don't count on this behavior, as it has been changed for 1.3A4. The
enforcing of the radio behavior will be done *before* the mouseUp
message is sent from then on.
Scott
> Boyd
>
>
-- *********************************************************************** * Scott Raney 303-447-3936 Remember: the better you look, * * raney@metacard.com the more you'll see -- Lidia * ***********************************************************************