You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to submit a PR that would align the text behaviors for CheckBox and RadioButton with some enhancements and fixes. These would be the main changes:
The text wrapping for CheckBox doesn't take into account spacing on the StatefulStackLayout and hence the text can overflow (fix for this)
Add the workaround for text wrapping that is used in CheckBox to RadioButton
Remove the maximum number of lines on the RadioButton (it doesn't exist on the CheckBox) or expose this as a bindable property on both if you deem it necessary
Align the label configuration of both controls
Expose a bindable property that would allow you to position the icon vertically. The main use case is when the text gets wrapped so the user can alter the location of the icon. Center is not always desired
Expose a bindable property that would allow you to position the icon horizontally. The main use case is when you have Vertical orientation. Center is not always desired
Expose a bindable property to propagate LineBreakMode
Expose a bindable property to propagate FontFamily
What is your take on this?
The text was updated successfully, but these errors were encountered:
Yes it seems right. You can take an action,
By the way sorry for my late response, I paused notifications from InputKit a while ago. I'm watching this repo again
I'd like to submit a PR that would align the text behaviors for
CheckBox
andRadioButton
with some enhancements and fixes. These would be the main changes:CheckBox
doesn't take into account spacing on theStatefulStackLayout
and hence the text can overflow (fix for this)CheckBox
toRadioButton
RadioButton
(it doesn't exist on theCheckBox
) or expose this as a bindable property on both if you deem it necessaryVertical
orientation. Center is not always desiredLineBreakMode
FontFamily
What is your take on this?
The text was updated successfully, but these errors were encountered: