I'm having the same problem I think. And from what I can observe here, you can't put any interactive content INTO a MSO - except buttons that would go to a specific state, (like go to state 2, tehn on state 2, a new button appear to bring you back to state 1).
You can't import or create a button into a specific state of the objet that would link you to an other page or an other document for example. Am I wrong?
You can integrate any function of buttons into a MSO accept another MSO.
Just build a frame, integrate it into the MS you want and give a function to the button (for example: weblink, web content, play movie, play sound … / there are more functions then “go to state“).
My mayor problem with buttons and MSOs is that you can't integrate buttons from the layout-layer. It's a pity because these buttons (witch opens MSOs etc.) will act when you are in a MS, too.
It would be a great if Adobe would find a solution to integrate any buttons into the States. And on top it would be the greatest if they find a way to integrate MSOs into a MSO ;-)
And one on top: a possibility to stop a video at the last picture … (dreaming of perfect publishing ;-)
Ok... So something must be wrong in my settings. I want to make a navigation menu which is a MSO.
In my simple example, you click on a "chapter 1" button, you have a pop-up with the sub-chapter entries (which is the 2nd state of a MSO), then I'd like to put links on these sub-menu entries to go to the different parts of the book. Each time I cop/paste the button, it loose its function.
After, but they don't work.
I group the buttons (with no instruction) to their respective image > then create an object state
so that one image has a "button" below it
and the next state has an image with a button further below that
then once inside the state I add the button instruction to both "buttons"
I want to do this so that when the state is not selected, the "button" area can not be accidentally tapped to move states
I know how to use the clear box trick that would acomplish the aesthetical side of what I wish to achieve, it just wouldn't do for the practical side.
1. Built a frame witch will be the button
2. Group it with the rest of the elemts that will be one state.
3. Activate all groups that will build the multi states
3. Build the multi state
4. choose the element (only) into the MS that will be the button
5. add the function to the element.
I do so all the time and it works.
If you place buttons into the different states with an action "go to next state" or "go to state (next wanted state)" for example for a full sceen gallery, it works without swiping:
- Layout-layer-button opens the MSO
- Buttons into MSOs with action "go to next state" in every state (also a second button with action "go to previous state" possible) But no back-button in the first state and no next state-button in the last state
- One more button on layout-layer with action "go to (first) state" act in every state and closes the gallery
I did so and it worked without swipe-action