react-native-slider
react-native-slider copied to clipboard
Unable to create Vertical Slider
Environment
Description
I am trying to create a vertical Slider. Based on #65 I got to know that transform can be used for this. Using transform I am not able to apply styles like height and width to slider.
Reproducible Demo
https://snack.expo.io/@yajana/slider
In my case height, width applies, but transform not applies automatically. when in the code i add style transform, then that applies. But when I reload the app, the transform not applies. On comment/uncomment the code, and directly viewing the slider in simulator then transform works, otherwise on reload of app transform is not applied
In case you're interested, in about a week I'll push a Windows implementation of this module, which will expose a 'vertical' prop to control this ;)
And is there any plan to implement it for Linux/Unix OS??
As far as I know, Linux is on not on the cards for the time being, though there are people requesting it, so who knows. However, there is parallel work happening for the macOS implementation by Microsoft: https://microsoft.github.io/react-native-windows/
Tacking on to say that we need a vertical prop for all platforms. Thanks!
As I can see on the provided example (thank you, @YajanaRao) the vertical slider is only inverted visually. Width and height still applies but with inverted effects, while sliding is still possible but also on the horizontal axis:
(notice the width change on the beginning from 30 to 300 <- it changes the height)
As I can see on the provided example (thank you, @YajanaRao) the vertical slider is only inverted visually. Width and height still applies but with inverted effects, while sliding is still possible but also on the horizontal axis:
![]()
(notice the
widthchange on the beginning from30to300<- it changes the height)
Why vertical prop is not working?
are there any updates for this issue?
@chiaramooney does the team still maintain these controls?
Unsure what callstack's status is, but sounds like this is an Android issue, so won't be tackled by the Windows team.