These changes to the ui would be essential for creating better experiences

for non-magazine stuff. I strongly support your requests.

with that adobe dps would fix many of the complaints from industry,

technicans and thinkers.

—Johannes

(mobil gesendet)

Hey Juergen,

if you are really desperate to disable horizontal swipe, you can put huge object on your pages that will catch the horizontal swipe, like a pan and zoom. and put a transparent image in it wich is just a pixel wider than it's container. That will catch the swipe and will not swipe the page in the end.

Your interactive buttons can go on top. However, you can swipe using the buttons.

—Johannes

As I understand it, this also covers HTML webcontents. The important thing

is, that is has to be scroll-able, so content needs to be wider than the

viewer frame.

A pan-only-overlay is just a webpage generated by indesign, displayed in a

webcontent container.

This catches horizontal swipes and keeps them after reaching it's own end.

Not for vertical swipes: when the end of an HTML file is reached, any

additional swipe will trigger the next-page-event.

I articles in my magazines where the reader basicly hits a "dead end"

article, where he cannot swipe along to get to the next article.

The desktop previewer is behaving differently. So this sounds more like a

bug/strange behaviour.

I know your crankamacallit. It is awesome how much workarounds you put in

there. I just hit everything to see how you did this and that ,-)

—Johannes

Has anyone tried this lately or come across a new work around? I tried several methods with buttons and underlying objects and it always swipes.

I would like users to be stopped at the end of an article where I have some navigation buttons taking them to another article, back to the index, or to the library. I also want readers to not be able to scroll "back" from the first page of each article. We are creating apps for collections of stories and they are not sequential.

Keith

I like a lot of the suggestions in here. But in thinking about what the tools can do, could you create the entire book as a MSO and then load that onto one page? Then you wouldnt have multiple pages, and you could create MSO navigation buttons. I dont know the extent of what is on your pages but it was just a thought.

Well, what if you create the entire page as a scrollable frame ie. paste all of the content into another frame (which is the same size as the page) and create a scrollable frame overlay, then upload the article as a PDF, the swipe to next page won't work (I've been having your problem in reverse!). You could then have navto buttons inside the scrollable frame to navigate. Just a thought...

Incidentally, I know that the swipe to next page is a problem with scrollable frames when uploading the article as a PDF, and the workaround was to upload as PNG, but this doesn't seem to work either. Anyone else having this problem?

in the v22 webinar I saw a little glimpse in the layout of amit Guptas

folio saying "User:Interaction enabled", so there might be somehow a

feature later — but that's a bold rumor.

—Johannes

I am also having the same issue as mobly, has anyone had any breakthroughs or updates recently?

I'm going to throw a spanner in the works! I create quite a lot of non magazine style apps, and don't mind the swipe to next page!

Still I can see it could be useful for some :-)

Alistair