En... weer(!) flinke bugs in de laatste update van DPS

.
Na de rampzalige update van de Folio Builder Tools en Panel van december (de ASCII-bug waardoor velen met voorgoed corrupte folios te maken kregen), is er bij de laatste update van 16/17 januari weer flink wat gebroken in DPS:

I just confirmed that not stopping at the last state of an MSO is a v18 bug. On the iPad viewer, selecting Auto Play and Stop at Last Image unfortunately stops at the first image.

The program team rebuilt the button and MSO overlays to enable embedded overlays. The testers tried to make sure that the rework didn't affect legacy overlays, but we missed this one.

To get embedded overlays to work, the program team rebuilt the overlays for slideshows and buttons. We expected to see bugs and limitations around nested overlays, but the team wanted to avoid introducing errors in existing areas. Unfortunately, a new slideshow bug prevents an autoplaying slideshow from stopping at the last image. It goes back to the first image on the iPad, This bug ruins fade-ins and other effects that rely on stopping on the last image. Other than using HTML, I'm not aware of a workaround.

While we can post hot fixes for the web client and Folio Builder panel, we can't easily post a new set of Folio Producer tools. This bug and others should be fixed in v19 (February), but that's several weeks away. If your design relies on stopping slideshows on the last image and you can't find a workaround, you should roll back to the v17 tools.

Dat niet alleen, gebruik je meerdere zelf afspelende MSO's op een pagina dan is de kans groot dat er maar een afspeelt en de rest niet.
En: gebruik je een sidecar.xml bestand (om namen en volgorde vast te leggen wanneer je een aantal artikelen in één keer upload) dan is het ook einde oefening: uploaden en updaten gaat dan niet.

UPDATE: het probleem met de MSO (objectstatus) zit volgens Adobe in de Content Viewer op de iPad , de Desktop Viewer geeft het wel goed weer maar dan wel met de laatste AIR-update. De panel-update van 26/01 lost helaas dus niets op... Folios met MSO's van eerder gemaakte Folios vertonen wel goed op de iPad, maar bestanden met MSO's gemaakt in de laatste Folio Producers vertonen niet goed op de iPad!


Nog een update: nog meer mis! De single-edition is ook verpest met de laatste update:

I have bad news. With the v17 viewer, the UIFileSharingEnabled key was set to "false" for Single Edition apps, but it was mistakenly switched to "true" with v18. Your options are to roll back to use v17 or wait until the next hot fix resolves this v18 issue. Sorry for the inconvience. Thanks for reporting this problem.

Ik vrees voor de cloud met vele updates straks voor de grote programma's.

Dit ge***** met DPS maakt wel dat het erg onberekenbaar wordt in DPS-tablet land...

Dan krijg je ook dit soort reacties op het forum:

Back from the meeting with the client: he's upset because he can't see what we have promised to him.

He asked: "Is this at beta stage this DPS thing?"
I said: "No, Adobe screwed the whole thing with the latest update."
Client: "Use the previous version"
I said: "No interactivity in MSOs. It's like suddenly the new version of Photoshop can't do what previous versions were able to do it but it is hard to use these old versions because we need the features in the new version".
Client: "Can we export the Folio as a standalone app and tweak them to make them work"
I said: "No, a folio does not use open-source that we can access in its binary and we are not expert in programming. It's not like HTML and JavaScript. Also you don't have the budget. Adobe creates tools only for very rich companies, the ones who can spend at least € 5,000 a year for only 5,000 complimentary downloads and with no guarantee for us, the agency, that we will have enough projects to cover the cost of the DPS contract."
Client: "Well, or you find another way to do it, or I choose another service supplier"
I said: "There are three possibilites: 1. we wait that Adobe fixes the problem but it will be too late for your project. 2. We make an iPad only version of your interactive publication and we use iBooks Author. This is free, easy and even spectacular. 3. We make hardcoded iOS (and Android) apps. But this is far more expensive."
Client: "The presentation must run on iOS and Android"
I said: "Let us think about it"

Thank you Adobe! It seems nobody in your team has real life files for testing apps before releasing them.

Ik wil niet al te negatief klinken, maar ik krijg ook de problemen voor mijn kiezen: leg maar eens uit tijdens een training waar cursisten goed geld voor betalen dat, wat ik ze leer moet kunnen, ook kon, te testen is op het beeldscherm maar helaas nu even niet werkt op de iPad!

Nee, niet best...


.