Each direct child of a Switcher module, with its own little group attribute, will comprise one active state of the Switcher - whether that state is being driven by a Pulldown or a Tabs module. However each of those direct children can have any number of other downstream modules. So if you want a bunch of different modules to show up under one active tab or option, you just have to create one direct child of the Switcher, and then put all your different modules downstream from that one direct child. If there's nothing at all that the different modules share in common, then the best idea is to use a NullModule as their common parent. Put the group attribute on the NullModule, the NullModule is of course the single direct child of the Switcher for your 3 charts, and then the NullModule contains various config downstream, notably all the stuff for your 3 charts.
If you check out the documentation in Sideview Utils - "Module Documentation > Advanced Modules > The Switcher Module", and you click the link there to "view xml source for this view", you'll see that a couple of the Switcher examples there have more than one module under a single Switcher branch. Admittedly there's nothing there giving the hint about using NullModule in cases where you want to group somewhat unrelated stuff together. I'll add something about that to that docs page in the next release.
