Sorry for that thing on the main timeline - this was just a quick example for the forum, and I did not notice it myself. It was the pausing of the other timelines that was the real problem.
Hi, I’ve read through this thread and am not sure about whether any implementations are suited for my needs.
I’m really thrilled with the new release of the blocs integration! Currently, I am working on embedding a few animations into the page, while hopefully having a few that would keep the current div or bloc in place while the scroll would create the parallax effect as highlighted in this thread.
Any pointers or suggestions on how to accomplish this? I imagine that some JavaScript would need to be embedded in blocs that would track a variable that would be published by the hype document.
Like: if div is in view and view played through is true then continue scrolling else continue timeline.
I don’t know JavaScript we’ll. Anyone have anything existing that may be able to work with this new integration?
The current Blocs beta has an option to associate scrolling to the Main Timeline in a Hype document, so it sounds like that will do what you want if it makes it into the final build .
I’m working on a project that probably will use your solution here (waypoints mhv1.hype.zip), but I need to improve it somehow.
My question is it possible the first square to be fixed to the top/bottom of the viewport and on scroll to trigger the animation to hide/show when viewport is moving across the scene?
Don't think it fails to trigger, looks to me like the chrome device is not respecting the viewport width.
In my tests at least for iPad size, it scales the page to 100%.
Safari's Resposive design seems ok. Since you are going to be using an iPad my suggestion is you test with that.
on the Simulator the Hype preview works well but very slowly, i also try to change Debug setting but nothing. I have a Macbook Pro i9 Big Sur...strange
It does seem a little buggy. Afer posting this I found that clicking a button seemed to hold it down.
I only new this because the button drives a stepper that changes a number.