@peabucket Please consolidate your questions to one thread. I am chasing all of your questions across numerous threads and they all involve the ability to utilize a bluetooth plugin with Onsen. Thanks!
Onsen UI shouldn’t be blocking the scroll event. The scroll event just doesn’t bubble (even without Onsen UI).
And since there is a specific element which is being scrolled, probably you’re just not attaching your listener to that element. In this case ons-page isn’t actually the element which is being scrolled. ons-page has a child .page__content which is the one which is being scrolled.
So if you just attach the listener to the element which is being scrolled everything will be fine.
Here’s a simple Demo of what you want to do if I understood correctly.
Keeping where the user left off could be done by keeping the current index of the carousel each time a change (slide) occurs.
Then, if the app should show the walkthrough page, it should do one more check to see if there is any index already set in localStorage. If yes then start the carousel on that index otherwise from the first.
@Fran-Diox FYI I’m still experiencing the same animation issue whether using rewritables or init to do the DOM attachment. You can see the bug in action if you access this on iOS, where you’ll see that the animation is completely broken because the element being attached (page-2-component.html) contains an ons-toolbar.
I understand it might not be considered urgent, although it does seem like a bug, since I can also reproduce the animation issue by doing other kinds of processing upon page init, not necessarily just injecting a riot tag into DOM.
edit: Tested on Android and there was no animation bug, so it’s only on iOS.