? I dont get this! PB can already do this with container gadgets and the option gadgets unselect others automatically. I dont get what else you need?Dare2 wrote:A command like GroupGadgets would be nice. This command would associated clumps of gadgetry and allow some actions to then be applied to all gadgets in a group. Gadgets should also be allowed to belong to more than one group.
It could be used for HideGadget, DisableGadget, etc, to do block actions.
eg:Some of this can be done in other ways (eg a procedure that does all the hiding/disabling/etc of a clump of gadgetry) but it would be neat.Code: Select all
... OptionGadget(#Option1,X,Y,40,20,"ONE") OptionGadget(#Option2,X,Y,40,20,"TWO") OptionGadget(#Option3,X,Y,40,20,"Whee") ... ButtonGadget(#ButtonA, etc) ... ComboBoxGadget(#ComboZ, etc) ... GroupGadgets(#Group1, #Option1,#Option2,#Option3[, ...]) GroupGadgets(#Group2, #ButtonA,ComboZ,#Option3[, ...]) ... HideGadget(#Group2,#True) SetGadgetState(#Group1,1)
For OptionGadgets it is a very intuitive way of lumping associated radio buttons together. So if one is chosen others in the group are unselected.
