I just finished a job that had about 20 states in an MSO with buttons in all of the states. It worked perfectly.
Without seeing your files is pretty hard to tell what, if anything you did wrong.
The only thing I can think of is to double check the slideshow pane of the Folio Ovelays panel and make sure everything is set up correctly.
Yes, this is a known issue. Your MSO needs to be triggered in some way to become a slideshow overlay -- either through selecting the Swipe, Tap, or Autoplay setting or by creating a button that points to the MSO. However, buttons inside a scrollable frame don't trigger the MSO, which is what you ran into. You can either enable Swipe, which you did, or create an invisible button with an MSO state action.
Just encountered a DPS article which we're planning to be the main navigation of the folio and, in order to create the interactivity, it looks like the correct way to have it work is an MSO with a large number of states.
We've started with one MSO with five states, and tried to have buttons within each state load a state in another MSO which would contain buttons to nav to the article in question - which isn't going to work.
So we could have a state in the main MSO with buttons that go to anothe state within the main MSO with a button that describes the link and takes you to the article in question.
The problem will be that if the original five states had say 10 buttons then we're up for 55 states in the resultant MSO - Are you with me so far?
The elements with the MSO will only be text boxes, but they'll be rasterised so will this cause problems in performance on iPad 1 viewers? Does anyone have a good general rule of thumb for the number of states which is going to start causing problems?
I know it's a bit of an open-ended question, but it's a fair chunk of work to create the MSO with buttons only to find it doesn't work.
Thanks in advance,