Hello all,
what is the reason that there is no WordWrap property/feature for TCheckBox, TRadioButton etc?
Regards
?ilvinas
Mailing lists / lazarus / 2010-06
Why no WordWrap in TCheckBox, TRadioButton etc
6 messages · 4 people · –
- zeljko 2
- Žilvinas Ledas 2
- Felipe Monteiro de Carvalho 1
- Hans-Peter Diettrich 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
?ilvinas Ledas wroteHello all, what is the reason that there is no WordWrap property/feature for TCheckBox, TRadioButton etc?
because it's not supported by all widgetsets (and even I don't know which one supports it).
zeljko
So, basically it means that TLabel is custom drwan and TCheckBox, TRadioButton are not?
zeljko wrote 17 lines
On Tuesday 22 June 2010 18:40, ?ilvinas Ledas wrote:
> Hello all,
> what is the reason that there is no WordWrap property/feature for
> TCheckBox, TRadioButton etc?
>
because it's not supported by all widgetsets (and even I don't know which one
supports it).
zeljko
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
2010/6/22 ?ilvinas Ledas :
So, basically it means that TLabel is custom drwan and TCheckBox, TRadioButton are not?
Indeed. But you can always create your own custom-drawn TCheckBox or TRadioButton.
Felipe Monteiro de Carvalho
So, basically it means that TLabel is custom drwan and TCheckBox, TRadioButton are not?
?ilvinas Ledas wroteSo, basically it means that TLabel is custom drwan and TCheckBox, TRadioButton are not?
TLabel is TGraphicControl while TCheckBox & TRadioButton are widgetset handles so they are basically TWinControls.Widgetset is doing complete paintings over those controls.
what is the reason that there is no WordWrap property/feature for TCheckBox, TRadioButton…
Hello all, what is the reason that there is no WordWrap property/feature for TCheckBox, TRadioButton etc?
It would complicate a form layout dramatically. Even if the new AutoSize may provide according features (dunno), GUI elements with varying heigth have to be accompanied by accordingly flexible containers (panels, groupboxes...), to be configured by the coder. The average user should not have to struggle with such features, that require a sophisticated layout of every single form, with unpleasant results when not all cases are covered by the design.
DoDi