fix bug with nextFrameID

[FredGithub]

Hello,

I had a problem with Sequence using the callback beforeNextFrameAnimatesIn. The problem occurs when using the pagination links : the nextFrameID variable don't have the good value (it has the value of currentFrameID). However, when using next and prev buttons, nextFrameID has the right value.

So i looked at the code and noticed self.nextFrameID is set in the next/prev buttons click handlers before the callback is called. But it isn't in the pagination handler. So i added it and it seems to work now

This is a one line change commit, so you might figure out quick if it's correct or not :)

Regards,
Fred

[IanLunn]

Thanks @FredGithub! 👍

[FredGithub]

Great :) You're welcome!

[martinAnsty]

Works great for this case, but there is still a similar bug where goTo() is called directly (nextFrameID is not correctly set).

Perhaps it makes more sense to set nextFrameID within the goTo() method?

[FredGithub]

Agreed. But this is too big of a change for me to do, I'll leave that to the creator

[IanLunn]

@FredGithub This is resolved now. @martinAnsty submitted a pull request and I made a few modifications elsewhere to tidy things up.