You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the seekTo() with function work so that all animation is complete prior to calling the function in the callback? ? If not how do I do this?
I've been working on a site (http://pie3.keene.edu/djc/index.html and the site uses your scrollable tool in conjunction with jQueryUI accordions and some ajax. I'm working on statefulness using hashes-
hash is read, looked up and a page index number and an accordion index is returned. Then I call the seekTo(index, function(){}) and within the function I make a call to open the accordion to the prescribed index. I'm finding that often when the site is responding to a bookmark, the page seems to be stopped 1/2 way through the scrolling to the page via seeTo() and the accordion is then opened. This sets the pages all offset by about 1/2 the screen- and I'm wondering if perhaps my call the the accordion API is being executed prior to the completion of the scrollable animation.
Can you assist? If there's no guarantee that the callback is waiting for the end of animation, is there a way to make this happen?
Best,
Dana
The text was updated successfully, but these errors were encountered:
I think rather than seekTo(index,function(){}) you need to do seekTo(index,speed,function(){}). Using the callback as the third parameter worked for me. In the scrollable documentation it says the method takes two parameters: index, and speed. However I believe there is a third parameter which is an optional callback function.
Hello-
First thank you for writing this cool tool.
Does the seekTo() with function work so that all animation is complete prior to calling the function in the callback? ? If not how do I do this?
I've been working on a site (http://pie3.keene.edu/djc/index.html and the site uses your scrollable tool in conjunction with jQueryUI accordions and some ajax. I'm working on statefulness using hashes-
hash is read, looked up and a page index number and an accordion index is returned. Then I call the seekTo(index, function(){}) and within the function I make a call to open the accordion to the prescribed index. I'm finding that often when the site is responding to a bookmark, the page seems to be stopped 1/2 way through the scrolling to the page via seeTo() and the accordion is then opened. This sets the pages all offset by about 1/2 the screen- and I'm wondering if perhaps my call the the accordion API is being executed prior to the completion of the scrollable animation.
Can you assist? If there's no guarantee that the callback is waiting for the end of animation, is there a way to make this happen?
Best,
Dana
The text was updated successfully, but these errors were encountered: