[iOS] RadioButton throws CGContextSetLineWidth - Fix#25542
Merged
PureWeen merged 2 commits intodotnet:mainfrom Nov 9, 2024
Merged
[iOS] RadioButton throws CGContextSetLineWidth - Fix#25542PureWeen merged 2 commits intodotnet:mainfrom
PureWeen merged 2 commits intodotnet:mainfrom
Conversation
kubaflo
added
area-controls-radiobutton
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
jsuarezruiz
suggested changes
Oct 28, 2024
Contributor
|
/azp run |
jsuarezruiz
previously approved these changes
Oct 31, 2024
|
Azure Pipelines successfully started running 3 pipeline(s). |
PureWeen
requested changes
Nov 2, 2024
| border.SetBinding(Border.StrokeThicknessProperty, static (RadioButton rb) => rb.BorderWidth, source: RelativeBindingSource.TemplatedParent); | ||
|
|
||
| // NonNegativeValueConverter ensures that StrokeThickness remains non-negative as the default value of -1 triggers a CGContextSetLineWidth error on iOS. | ||
| border.SetBinding(Border.StrokeThicknessProperty, static (RadioButton rb) => rb.BorderWidth, source: RelativeBindingSource.TemplatedParent, converter: new NonNegativeValueConverter()); |
Member
There was a problem hiding this comment.
Can this be fixed inside the Border control?
So the border control could also check if this value is getting set to -1?
This fix feels isolated to only fixes RB's use of Border vs border as a larger use case
kubaflo
force-pushed
the
fix-25273
branch
2 times, most recently
from
0dd9c15 to
6db3d42
Compare
Member
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
PureWeen
approved these changes
Nov 8, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Change
The error occurred because the default value for Border.StrokeThickness was set to -1. Instead of changing this default to 0, I implemented a converter that ensures Border.StrokeThickness never receives negative values.
Issues Fixed
Fixes #25273