Oh and I don't think it's the new Content Viewer app, I get the same results using a custom viewer builder app ( v18 ).

Yeah good point.

Thanks for confirming.

Hopefully there's a hot fix soon.

GP1 not sure what you're trying to fade but for my text title fades I'm going to just use the HTML5 method.

Hi Bob,

Long time listener, first time caller :-)

This bug is driving me crazy. I had so many nice page effects going on and now can't use any of them...I don't really want to roll back but might have to.

Any ideas when the next release will be in Feb?

Thanks,

Rob

I am getting similar behaviour with a multi state (2 states) that has two pannable images.

Procedure followed:

1. Place img in large frame;

2. Cut frame, paste into smaller frame;

3. Select pan only overlay for smaller frame;

4. Cut smaller frame;

5. Paste into state 1 of multi state;

6. Repeat 1-5 for second image/state 2.

Output: works flawless in desktop preview, but multi-state invisible on pad. Interesting note: multi-state is in the folio somehow, because touching in its location shows scrollbars, just not the content images...

Is my procedure wrong, or is this a similar or the same bug?

@Bob, can this be added to fixlist?

Hi Bob,

Do I need to install a new version of Folio Producer with Viewer Builder to make sure these fixes work on my and clients' pads when they download the folio for testing?

Thanks, d

[quote] You do not need to update your Viewer Builder. Use the Viewer Builder to create a new custom Content Viewer or custom viewer app. A new version of the Adobe Content Viewer will not be submitted to Apple, so the only way to take advantage of these bug fixes is through the Viewer Builder.

[/quote]

?????

Excuse me?

What does this mean for all the workgroups I teach coming weeks and are testing on their iPads? They just can forget about showcases on their devices untill...  Untill what or when?

Na, do not understand this AT ALL...

[QOUTE]

Option 1) Use the current tools. In your workgroups, avoid MSOs that hit the bug areas (timing and stop on last image). Or include it and mention that it's a bug with the current iPad Content Viewer, but it works as intended on the Desktop Viewer.

Option 2) Roll back to v17 tools. Your MSOs will work, but you won't be able to demo nested overlays in slideshows or other v18 features.

[\QUOTE]

Exactly. That was what I don't understand - that this is indeed so.

I'll mention the bug and the policy in resolving the bug.

It will not go down well...

> and I'm not sure what your lectures comprise of, but I'm assuming they can't be completely reliant on features that have just been released, the most sensible option for you would be to roll back to v17 and work with this.

Not completely anymore no, because of the bugs! But 1.7 won't allow for PDF zoom on interactive pages. Would love to show and teach that.

Do you fully understand how this is: telling them, no, will not preview on your iPad (same for shared folios!!) or loose functionality and revert back to 1.7

Simply not to sell to clients this message....

Johannes,

do you see differences between rendering new interactive elements from the uploaded folio versus folio displayed via USB?

Or is it only me? My tests come out OK via USB and fail with vanishing text  when downloaded from the cloud.

Tomek

New tools that are pushing the bounderies for designers to work without code are always going to have teething problems.

Although its frustrating I think the tools are going to be great. We have to remember the suite is still being developed and we are lucky enough to have Bob who listens and feeds back to the development team.

(On that note...buttons with MSOs please bob )

Thanks Klaasjan. And good luck with that list of bugs! ,-)

Printer has a client, client wants to see what is possible. Client likes, then order in. Now printer wants to show real iPad example before investing money when client likes. Can't show on actual iPad the nice MSO because broken on iPad. Client does not trust. Build Viewr App you say? No Mac just Windows!!

Bob, real life out here  in actual cases means people loose orders and trust...

It is very unfortunate that the App Store version of the Content Viewer is not able to be updated to fix major issues discovered after tool udpates.  From the outside it seems that Adobe doesn't understand just how many people use the App Store (and Android market) version of the Content Viewer as a selling, testing, and distribution tool.  If we could control when the app is updated for customers then it wouldn't be as big of a problem, but they are notified of the app update and usually install it immediately.  If there is some way in the future to overcome the problem of unintended bugs in the Content Viewer not being fixed until the next official build it would make using and recommending Adobe's DPS much less nervewracking.  The potential for missed deadlines, disappointed/frustrated current customers, and losing out on future business is very high with the way things currently are.  It can also ruin your day/week when a folio that was able to be viewed perfectly on Monday won't even load on the same device on Tuesday because of an update to the Content Viewer.

The Adobe Content Viewer is a fantastic part of the system and a great way for clients to review work, etc.  Making it a reliable tool is a needed improvement.  Perhaps there can be a Content viewer in the app store(s) that isn't updated until all major bugs in the latest tools have been discovered and addressed.  This would be the Content Viewer we point customers to.  The current way the Content Viewer works could be retained for developers to test their folios and find bugs with the latest tools.  Not having that level of reliability in the system means we have to apologize quite a bit for things that aren't our fault and, as others have noted, can lead to losing potential customers.  There will never be a bulletproof way to perfectly update complex software and hardware the first time, but if we can have a plan for dealing with the inevitable imperfection it will go a long way in making Adobe's system the standard for the quality and reliability that professionals seek when choosing their tools.

Andrew

My guess on the bigger picture is this: at current, DPS is ahead of everybody, but there must be pressure coming from Apple's recently launched iBook Authoring tool, which is currently focussing on text books, but provides interaction as well. It does not offer the functionalities of DPS at the moment, but it is a free tool. If the rapid evolution of Xcode is any indication, we could see a full suite of iBook and maybe also iMagazine authoring tools, for free, within 24 months. In that scenario the only way for Adobe to keep its position in a 2-5 year time window is in adding a large number of functionalities and by doing so keeping ahead of the competition. This means the pressure on new releases is big and time and resources spent on testing may suffer...