Skip to content

@slidy/core: end custom event #67

Description

@EricRovell

In case the loop mode is not used, it makes sense to have a on:end custom event for the core packages.
@Valexr , what do you think about it?

Activity

  1. Valexr commented on Mar 11, 2022

    @Valexr
    Owner

    In case the loop mode is not used, it makes sense to have a on:end custom event for the core packages.
    @Valexr , what do you think about it?

    What for on:end? 😁

  2. EricRovell commented on Mar 11, 2022

    @EricRovell
    CollaboratorAuthor

    It would indicate that the navigation finishes. Would be useful, for example, to use it for lazy loading more slides.

  3. Valexr commented on Mar 11, 2022

    @Valexr
    Owner

    It would indicate that the navigation finishes. Would be useful, for example, to use it for lazy loading more slides.

    When navigation finished? I’m don’t understand what you meant…🤷🏻‍♂️

  4. EricRovell commented on Mar 11, 2022

    @EricRovell
    CollaboratorAuthor

    It would indicate that the navigation finishes. Would be useful, for example, to use it for lazy loading more slides.

    When navigation finished? I’m don’t understand what you meant…🤷🏻‍♂️

    When you navigate to the last item.

  5. Valexr commented on Mar 11, 2022

    @Valexr
    Owner

    It would indicate that the navigation finishes. Would be useful, for example, to use it for lazy loading more slides.

    When navigation finished? I’m don’t understand what you meant…🤷🏻‍♂️

    When you navigate to the last item.

    I think this task already done🤓 info about last item available in the on:move event in event.detail.index 🤷🏻‍♂️

  6. EricRovell commented on Mar 12, 2022

    @EricRovell
    CollaboratorAuthor

    You are correct. It can be implemented by user, Still, even if it is simple, I think it would be quite useful to have this kind of event. Let this issue live for some time, maybe someone will find it and ask for it. If not, we will close it.

  7. Repository owner locked and limited conversation to collaborators on May 5, 2022
  8. converted this issue into a discussion #71 on May 5, 2022
  9. removed this from @Slidyon Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestquestionFurther information is requested

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions