I really dont think you should be so self concratulating I have come back to DPS after using the pre-release version last year, and yes it has the potential to be a good system, but at the moment its a mess. The way the latest release has been handled is typical

For one, the new Scrollable Frame option does not work correctly: you can slide up from the bottom, but you can not slide down again (sliding from the left/right side does still work)...

And pasted into frames are cut off and have some parts not showing.

In other words: new feature, nice idea, but is not usable at this moment.

i'll try this afternoon, i hope. Will let you know.

Martin Lér wrote:

 

i'll try this afternoon, i hope. Will let you know.

Hm, seems that it will take some time... But maybe Johannes or Tomek can help me . Recetly (week ago) we came to second year of our iOS development program. So i recreated our developer and distribution certificate. Today i've created new version of Adobe Content Viewer with Viewer Builder, uploaded to Testflightapp.com and... i can't install it to our iPads. Installation will start, but before end it will stop with error, that app can't be installed now (very unspecific error). I think that it can have something to do with new certificate, but i'm not iOS dev guru, so i'm now little bit lost. From my understanding i don't need to recreate provision profiles, so i'm using old ones. Anyone some idea? Thanks a lot!

Tomek, problem will be not with Viewer, but with my certs. So my question is more iOS-development related (i know that this is not best place

Yeah, i forgot abour referencing dev certificate in mobileprovision, in meantime i checked it and recreated mobilprovi. Now it works and i can test error .

OK. I have tested Johannes' bug on three MSOs made from scratch.

The bug is persistent, it appeared in all three MSO.s. On the first 

run, every change of state produces background blink (Tested with 

white, black and pink bckgnd). In one case, I had also incomplete 

renderening of some states, with background showing from beneath.

This incomplete rendering did not disappear after first run.

All folios were tested both as uploaded and via USB.

Both. As a matter of fact I also tested one MSO with light grey letters on dark background ( no images, just indesign text and fill), and the effect/bug was just the same.

Tomek

just curious... is the problem occurring on both iPad 1 and iPad 2?

Hello Johannes and Tomaz any of you found a workaround for the fade in MSO behavior? I'm using several MSO's to set elements on top of ther interactives and those behind are revealed the first time the MSO plays...

Anyone from Adobe can confirm this bug?

Thank you.

I am also experiencing some erratic behavior from sideshow MSO's. 

I am using v19 Tools, Builder, and Content Viewer on both the iPad2 and iPad3.

I can confirm the flash to white between the initial run through of the slides.  Also I have noticed that on Desktop viewer (have yet to test on v19 Content Viewer on iPad2 / 3) the state that is selected in the layout .indd file flashes before showing the desired initial state of the MSO sideshow.

So to be clear.  If I create a MSO sideshow and have any state of that MSO selected in the Object States palette that is NOT the intended inital state, the selected state will appear quickly then revert to to the desired initial state when previewed. 

Will test on iPad to see if this behavior remains across viewer types. 

Good news is this is an easy fix by simply making sure to have the initial state selected prior to uploading to producer although this would be a new best practice.

Any others experiencing the MSO slideshow "jump"?

-Tony C

@mpm_iPad and Everyone above with the MSO problem in v19

How are you previewing the MSO(slideshow)? Are you previewing using the preview on device option directly from InDesign? If yes, I get the same error and looks like this is a bug to me or something that's specific to the iOS webkit rendering or something that Adobe needs to fix it with Apple.

But the preview on the newly custom built Adobe content viewer works fine as expected and shouldn't be a problem on live app. I have tested and confirmed by building a viewer app.

So basically, you need to login to the Adobe Content Viewer on your iPad and download the folio and preview. So, to avoid any unexpected MSO behaviour, the best work around is to login, download and preview and not preview directly from InDesign. Hope this helps :-)