Is there a known issue with listener calls on the FSlider?

[georryan]

I'm currently running version 0.10.0+1. I'd like to proof of concept out some of my ideas before upgrading and fixing all the breaking changes in the next update. I'm running into an odd issue, though. I have an FSlider with a listener handler for responding to the slider changes. That works fine.

I've been trying to automate the slider with a play/pause sort of functionality and have it loop once it gets to the last mark. If I use the "controller.step(min: false, extend: true)" method within my timer call, I can animate the slider stepping through all of its values and make it to the end of the slider. If I call the "controller.slide()" method and pass in the offset value as a literal, the FSlider will adjust on the screen correctly. When I call that same slide() method and pass it the same value, only now that value is in a variable, the Slider never advances and the listener handler never gets called.

I may have to bite the bullet and make the update. Maybe the onChanged event would be better than using the controller and listener handler, although I'm not sure how to assign a value programmatically without the controller? Anyway, just curious if I likely have some other issue I haven't discovered or if this is a known issue?

I guess another workaround would be to use the step method until I get to the end, and once at the end, call the slide method with a literal of the first value. After looping like that, I can go back to the step method.

[Pante]

I can animate the slider stepping through all of its values and make it to the end of the slider. If I call the "controller.slide()" method and pass in the offset value as a literal, the FSlider will adjust on the screen correctly. When I call that same slide() method and pass it the same value, only now that value is in a variable, the Slider never advances and the listener handler never gets called.

Could you elaborate on this/potentially provide a code snippet? It'll make it easier to evaluate if it a bug and whether it has been resolved in the latest version.

[georryan]

While setting up a simple code snippet I was able to get it to work fine. So the problem is with the user somewhere. I must have something wrong in my app that is getting in the way.

Sorry for the false alarm!

[Pante]

No worries! Please do reach out again if you manage to reproduce it!