-
-
Notifications
You must be signed in to change notification settings - Fork 496
Problems with initial rendering and "rzSliderForceRender" - "bullets are aligned at left side" #116
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
On what object do you want to add these methods? |
I didn't check source code and general architecture but ideal situation for me when you can add it like a dependency to the controller:
Or add any other way to render slider after some events. |
I didn't noticed on your first comment, but you don't need to broadcast on the root scope. Just on the controller scope where the slider is included. Then, the RZSlider service is a factory on which we call |
I am also experiencing same issue. can anyone tell me how to use rzSliderForceRender ? |
See #79 |
Same for me here, tried with all the broadcasting events like reCalcViewDimensions and rzSliderForceRender, giving any kind of timeout but still getting the same problem. |
AHAHAHAHAHAHAHAHAHAH Ok sorry Valentin, I'll try to but the app is kinda big. I'll be back soon, 2016-07-29 10:18 GMT+02:00 Valentin Hervieu notifications@github.com:
|
Hi All, I am implementing Rzslider for time range But I am facing some issues. And I already ask in stackoverflow Please look at this. https://stackoverflow.com/questions/45429746/dont-lose-previous-position-of-rzslider-after-select-the-date-in-angular-js?noredirect=1#comment77835931_45429746 |
I added a comment on Stack Overflow ;) |
In some projects slider rendered wrong(bullets are aligned at left side) from the initial view join. Also well known bug with ng-show/ng-hide usage. This bug partly can be solved by using "timeout" and "rzSliderForceRender". But that is ugly solution:
Solution: introduce public interfaces ".redraw()", ".reset()".
The text was updated successfully, but these errors were encountered: