Hello Jens and Torsten, > And I am also concerned that we might make the API misleading when we pretend > that those segments are full featured buttons, when we in effect really only > use them as data models for the parent item, ignoring any other properties > and behavior they may have. In traditional Qt there was something called a > QButtonGroup which was a purely logical element. It could be used to > enable/disable a group of buttons and control their exclusivity. It did not > affect the appearance in any way. In this case, both Button and RadioButton > would work fine. However, the SegmentedButton seems more like a widget by > itself that has more in common with a Tab Bar than a button.
I agree with the idea of thinking about it as a widget on itself. And maybe even taking a model instead of having child items could be something to explore. Having a "full-featured" Button adds the expectation of being able to do the same tweaks that you can do to a Button, raises the question whether we can use other Button-like components, etc, which I am assuming is not the case. Cheers, -- Caio Marcelo de Oliveira Filho OpenBossa - INdT _______________________________________________ Qt-components mailing list Qt-components@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-components
