11 Replies Latest reply: Sep 8, 2012 2:55 AM by marcbackwell

Sluggish button performance

stubs2345 Jul 26, 2012 6:56 AM

Simple nav in any of my folios seem to take forever and it's starting to get me down ;-) I must be doing something wrong. Go to destination or Go to URL buttons take a considerable amount of time - around 2 seconds to do its thing. I can't imagine it's my file sizes, and I've been building portfolios to standard iPad res and retina with no difference. It's just slow...

Any ideas on how I can make things more snappy? Thanks very much.

1. Re: Sluggish button performance

Neil Enns - Adobe Jul 26, 2012 9:32 AM (in response to stubs2345)

Out of curiosity, are you creating folios as PDF or PNG?

Neil
Like Show 0 Likes (0)

Actions
2. Re: Sluggish button performance

stubs2345 Jul 29, 2012 1:13 AM (in response to Neil Enns - Adobe)

Thanks Neil. Just recently back using DPS and didn't realise the difference between PNG and PDF. The PNG works fine - nice and responsive. I must say that PDF is practially unusable IMO - the performance is so poor. Shame really as that would be my preferred option.
Like Show 0 Likes (0)

Actions
3. Re: Sluggish button performance

Johannes Eckert Jul 29, 2012 1:17 AM (in response to stubs2345)

PDF is really hard to use, especially with big images in the ipad3.
there is a photo magazine "leveled" wich is nearly unswipeable.

(mobil gesendet)
Like Show 0 Likes (0)

Actions
4. Re: Sluggish button performance

mobly Jul 30, 2012 8:37 AM (in response to Johannes Eckert)

Plus with PDF you get interactive areas that become dead zones to swiping. It's a big problem, as without PDF, retina apps will be huge. I just download Backpacker magazine (August) which was 1.5Gb
and thats just ridiculous for a ordinary Mag. Still work to be done :-)

Cheers
Alistair
Like Show 0 Likes (0)

Actions
5. Re: Sluggish button performance

Neil Enns - Adobe Jul 30, 2012 10:04 AM (in response to mobly)

We've fixed the problem with swiping not working on scrollable frames in PDFs. It will release with our v22 build, hopefully next week. Yay!

Neil
Like Show 0 Likes (0)

Actions
6. Re: Sluggish button performance

BobLevine Jul 30, 2012 10:06 AM (in response to Neil Enns - Adobe)

WOOOOOOOOOOOOT!
Like Show 0 Likes (0)

Actions
7. Re: Sluggish button performance

Neil Enns - Adobe Jul 30, 2012 10:08 AM (in response to BobLevine)

I agree.
Like Show 0 Likes (0)

Actions
8. Re: Sluggish button performance

Johannes Eckert Jul 30, 2012 10:13 AM (in response to BobLevine)

is it possible To swipe to the next article on vertical swipe areas as well?

(mobil gesendet)
Like Show 0 Likes (0)

Actions
9. Re: Sluggish button performance

Neil Enns - Adobe Jul 30, 2012 10:15 AM (in response to Johannes Eckert)

Yes, I just tried it. If you have a vertical scrollable frame in a PDF stack, a horizontal swipe on the frame goes to next/previous stack.

Neil
Like Show 0 Likes (0)

Actions
10. Re: Sluggish button performance

Johannes Eckert Jul 30, 2012 10:32 AM (in response to Neil Enns - Adobe)

great, thank you.
—Johannes
Like Show 0 Likes (0)

Actions
11. Re: Sluggish button performance

marcbackwell Sep 8, 2012 2:55 AM (in response to Neil Enns - Adobe)

I am still having problems with scrollable frames with the article uploaded in PDF format. I've read that Viewer v22 has solved this but not for me me. I have the latest Folio Builder as well as the latest version of Content Viewer on my iPad. I have saved my Folio as v22 in PDF format and imported my multi-orientation articles as per normal. However, there is STILL a problem when trying to swipe across as vertical scrollable frame - it simply doesn't work. When I add articles individually, and as PNG, the swipe across the scrollable frame then works, but then the ipad is extremely sluggish when changing orientation ie. it takes 4 to 5 seconds to change from one orientation to the other, which obviously won't be acceptable. I've read on some forums here that although the PDF option won't work in the Content Viewer, it will work on published Folios, but this is no help if I'm using the Content Viewer to try to sell an app idea to a prospective client. Does anyone else still have this problem?
Like Show 0 Likes (0)

Actions