Jup. Bug/different behavior with PDF articles. Use png format on these
articles if you need this.
NORDSUEDDESIGN Büro für digitale Kreation
+49 177 629 63 55
I also had this problem in the Adobe Viewer app, but not in the developer viewer app build with the viewer builder (single edition app), as long as you don't activate PDF zooming.
So if you're planning a single edition app, try exporting the folio and building your own viewer app.
I didn't realise you can mix the article formats within your folio. That is better that you can mix it up with PDF and PNG.
I found that when i used auto detect on my scrollable frames I had a similar problem. If you specify which way you want to scroll (vertical or horizontal) then it should be ok.
Thanks for reporting this guys, I've asked our team to open a bug.
I reported this over a month ago. I also reported it as a bug. Hope it gets fixed but I'm not sure it will as Zeche said in the last webinar that you guys are looking to introduce some kind of "swipe zone" that could sit over a scrollable area. That wouldn't be necessary if the PDF issue could be fixed!
Having some pages that are pinch and zoomable and some not, gives a confusing user experience, in my opinion.
Perhaps better to have just hot areas/images for pinch and zoom like the old days.
We've introduced hot zones (tappable areas to navigate between stacks) in an update to the v20 release.
Wait….tell us more!
You need look no further than Bob's excellent What's New notes. There's mention of it there, and a link to the following in our documentation:
Enable “hot zone” Navigation
If you select this option, invisible hot zones appear on the left and right sides of every article (or page if the article scrolls only horizontally). Tapping a hot zone jumps to the next or previous article. Hot zones are especially useful for full-screen overlays, such as slideshows If an overlay appears in the hot zone area, tapping that area activates the overlay, not the hot zone, unless the overlay is full-screen (covering at least 95% of the viewer area).
That’s wonderful…for Enterprise, but that doesn’t help the majority of the users.
I’m working on a Single Edition project and quite frankly this behavior makes no sense (especially since it only happens with PDF articles). If we specify the scroll as vertical only then the article should swipe horizontally.
I realize this is a work in progress but this is really something that I think needs to be looked at in a future update.
I haven't done a comprehensive QA to see if I'm doing something wrong - but tapping on a Hot Zone within a JPG rendition of a folio smoothly navigates from page to page - just as advertised!
However, tapping on a Hot Zone within a PDF rendition of the same folio causes the Nav bar to activate. The page advances properly...but the activation of the Nav Bar is awkward.
It is indeed awkward. The engineer sitting across the table from me confirmed this is fixed for release 21.
Cool - thought I had mixed up too many things...
btw Zeke never talked about scheduled R21 features on the R20 demo on the 21st. Is there anything posted?
I don't know, sorry. I wasnt in that session.
I take it the enterprise boys have just got this feature I bit early??
And pro users at the next release??
bugs and behaviour like this is a suspicious sign of a wrong architecture,
too many cooks/programmers ruining the menu (a German spoke word), or
DPS is a massive complex system.but for these, data models and information
architecture are critical to success.
I see movement at adobe here. there are more and more people from adobe
responding to problems, actually engineering on these forums and more
concise product management. one can feel that.
but sometimes, these "funny" things happen... they don't matter to the big
publishers still on sprint 15 or enterprise level publishers with their own
track if DPS (visible in the cryptic version number for the WIRED reader
but they matter to the designers, makers, thinkers and people on the
bleeding edge of DPS actually trying to produce stuff and stumble upon
... and we never heard anything about the plans of R21 in this session or