I would love to see the Auto Scroll extension added to the Dynamic Slider.
This would greatly expand the potential use cases, with only a small addition of code.
So far I have used keyframe animations for this, but that is always a bit fiddly, not as smooth, and also quite restrictive. You simply cannot access many integrated options with this approach.
Thank you for considering.
Hi @Marius,
Please correct me if I am misunderstanding this request, don’t we already have auto scroll for the dynamic sliders (that use Splide) in Cwicly?
We have Autoplay, which basically mimics a user interaction at a set time (interval). It slides (for the specified number of slides), but does not scroll consistently/smoothly.
When I see the transition value from your screenshot, it suggests that you wanted to create exactly this effect. 40 seconds as a duration of one sliding action seems a bit high to me.
This slider must be veeery slow 
Or you are sliding all slides at once.
Got you, we are talking about a continuous scroll effect
Yes, we have emulated the auto scroll using settings, using an interval of 0 and a long transition gives a very close approximation. 
That’s what I thought.
While this emulates the effect, there might be issues with dragging, pause on hover/focus, etc.
It is the best option available given the limitations of splide and we have used it on several sites without any significant issues.
I agree, having a dedicated way to do this properly will be much better
Here is a demo of the emulation that can be achieved with the current auto play options as described:
I think the main point is the speed parameter and its calculation, also without the necessity to define the total amount of slides. This static value always has to match with your query settings.
As a forced workaround, its fine. But it’s not a real solution imo.
Especially when a client is in control and has no clue about the dependencies.
Auto Scroll is set and forget.
I’m really happy to see that it already has changed to planned.
The UI, in most parts, is already there.
PS:
Thanks for sharing your workaround though, hadn’t thought of that before.
