Carousel - Auto=true does not repeat cycle #1461

Closed
opened 2026-01-29 17:53:56 +00:00 by claunia · 5 comments
Owner

Originally created by @Anspitzen on GitHub (Nov 6, 2024).

Describe the bug
On Auto rotation the carousel will stop on last item

To Reproduce
Steps to reproduce the behavior:

  1. Go to official demo
  2. Go to last item or wait until it is there
  3. See error

Expected behavior
Rotation should start again

Desktop (please complete the following information):

  • Browser Chrome
  • Radzen Version 5.5.4

Additional context
Broke with bb675ee because Timer has GoTo(selectedIndex + 1) which will just be out of range and not navigating

Originally created by @Anspitzen on GitHub (Nov 6, 2024). **Describe the bug** On Auto rotation the carousel will stop on last item **To Reproduce** Steps to reproduce the behavior: 1. Go to official demo 2. Go to last item or wait until it is there 3. See error **Expected behavior** Rotation should start again **Desktop (please complete the following information):** - Browser Chrome - Radzen Version 5.5.4 **Additional context** Broke with bb675ee because Timer has GoTo(selectedIndex + 1) which will just be out of range and not navigating
Author
Owner

@Anspitzen commented on GitHub (Nov 6, 2024):

Should I open the next bug report? Because now the tiemr will reset itself every time (Next() is calling to Navigate which is reseting timer) which was deemed not nice on commit 0466912

@Anspitzen commented on GitHub (Nov 6, 2024): Should I open the next bug report? Because now the tiemr will reset itself every time (Next() is calling to Navigate which is reseting timer) which was deemed not nice on commit 0466912
Author
Owner

@enchev commented on GitHub (Nov 6, 2024):

The timer will reset itself on every navigate no matter if it's from the timer or not. What's the problem with that?

@enchev commented on GitHub (Nov 6, 2024): The timer will reset itself on every navigate no matter if it's from the timer or not. What's the problem with that?
Author
Owner

@Anspitzen commented on GitHub (Nov 6, 2024):

On the Navigate there is an explicit call to Timer.Change(); function.
Thats the only thing that was different on the GoTo call on timer itself, was made that way on #1741
Edit: Basically I just confused which way it should be now, just to better my understanding

@Anspitzen commented on GitHub (Nov 6, 2024): On the Navigate there is an explicit call to Timer.Change(); function. Thats the only thing that was different on the GoTo call on timer itself, was made that way on #1741 Edit: Basically I just confused which way it should be now, just to better my understanding
Author
Owner

@enchev commented on GitHub (Nov 6, 2024):

Yes, that's how should work in my opinion - the navigation should take the same route no matter if initiated by the timer or manually.

@enchev commented on GitHub (Nov 6, 2024): Yes, that's how should work in my opinion - the navigation should take the same route no matter if initiated by the timer or manually.
Author
Owner

@Anspitzen commented on GitHub (Nov 6, 2024):

Ok, then everything is good. Thanks for clearing that up for me and thank you for your work

@Anspitzen commented on GitHub (Nov 6, 2024): Ok, then everything is good. Thanks for clearing that up for me and thank you for your work
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1461