Helps connecting a Hype document to the history object
I don’t understand what your question is. HistoryKit uses the browser History-API (like the back and forth buttons) so I am not sure what you want to achieve in placing buttons at diffrent heights of scenes. Using HistoryKit is the same as planing for a regular navigation that makes sense.
Do you mean scroll restoration?
Thank you for providing this great extension for hype. You mentioned the possibility of being able to push state manually. In theory that sounds very useful to me - but I’m not sure what implications there might be in restoring a scene that has been modified/animated etc? Is that easily ‘serialised’ and then deconstructed, or would it be very involved?
If a manual history push state is relatively easy for you to achieve then I would definitely appreciate it
(A) This is the place to store data to a state (as an object), state is ONLY pushed on sceneLoad
(B) In this IF-branch the state gets restored. You would need to restore whatever you stored here to reflect in Hype (timeline setting or something)
This is still a 1.0 … and as I haven't gotten much qualified feedback on this one I never developed it any further but it should do the job. If you need to push states not depending on scene changes the code would have to be changed/further developed or you could just develop your own in that case as this is only a very thin wrapper.