This repository has been archived by the owner on May 1, 2024. It is now read-only.
[Enhancement] iOS PlatformSpecific for UISlider #1729
Comments
I would like to take this one. @davidortinau |
@ctartamella still working on this? |
@davidortinau I'll take a look on this now as it seems like there is no active work going on. Let me know if there is. |
henricm
added a commit
to henricm/Xamarin.Forms
that referenced
this issue
Apr 16, 2018
4 tasks
henricm
added a commit
to henricm/Xamarin.Forms
that referenced
this issue
May 3, 2018
henricm
added a commit
to henricm/Xamarin.Forms
that referenced
this issue
May 3, 2018
Adding null-checks when receiving gesture event since control may have been disposed/removed at this point. Making sure to remove GestureRecognizer when disposing renderer. Refs xamarin#1729
rmarinho
pushed a commit
that referenced
this issue
May 3, 2018
…1729 * Adding support for tapping on iOS Slider to set value Refs #1729 * Remove GestureRecognizer and added null checks Adding null-checks when receiving gesture event since control may have been disposed/removed at this point. Making sure to remove GestureRecognizer when disposing renderer. Refs #1729
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rationale
There is currently no way to to set the value when tapping a slider on iOS
Implementation.
Add a PlatformSpecific property for Slider on iOS. Customer renderer changes to subscribe to the tap event, calculate position and set the value. `((IElementController)Element).SetValueFromRenderer(Slider.ValueProperty, Value)
Expected Result
Android
None
iOS
Value of slider should be updated when tapping
UWP
None
Implications for CSS
None
Backward Compatibility
We should set default to false and make sure all custom renderers continue to work even with our implementation.
Should respect and have some UITest for InputTransparent and and IsEnabled properties.
Should work with a tap gesture by allowing bubbling of the event to the parent.
Difficulty: Easy
The text was updated successfully, but these errors were encountered: