Having a button to serve as an 'orchestrator' is not a problem but I am
looking for a more elegant and promptly way of processing the clicks; the
scenario I envision is goes like this: the user clicks a checkbox ( checks or
unchecks it, that is not important at this moment), the checkbox broadcasts a
'they clicked me' event with additional data, my own handler consumes this
event and processes its data ( what is the id of the box, was it checked or
unchecked, ...) then pases it on. Is that feasible? But maybe this gets too
low-level ...

"OssieMac" wrote:

Hi Mac,

I think that best way to handle this is to have a command button called
Continue or Next otherwise you will never know when the user has finished
making the selections. The user might just make one or two selections or many
more selections. They might even change their mind and uncheck boxes that
they previously checked.

You can test each check box for true or false after the command button is
clicked.

--
Regards,

OssieMac