I am having some problems creating buttons in object states...I have a colored rectangle and a text box in each object state...I have selected the rectangle as the button to show the next state (there are only 2 states) and the second state leads back to the first one...
but in some of the object states the text box does not appear? if i don't have the second state as a button then it appears ok (but I can't return to the first state)
any ideas? do i need to group each text and rectangle before placing it into the object state and subsequently making it a button?
Buttons in object states that navigate to the states in the MSO can be created outside of the MSO but once placed into that MSO will lose their go to state or go to next state functionality.
This is a long standing problem and quite frankly a major PITA. The only way around it is to add that function after putting the button into the MSO.
@Bob – however, if you group an MSO with buttons inside, the targets (object states) in the buttons are wiped out. Un-group does not bring them back.
At least that will happen in InDesign CS5.5 v7.5.3.
And: if you copy/paste a button on the page (not inside an MSO) the pasted button will loose its target, if the target is an object state.
I don't understand that first one. To be honest on the second point, I've gotten into the habit of putting all buttons into the MSOs. The go to state thing is a pain, but it's way easier to manage.
@Bob – sorry, Bob. I'll try to explain again:
Say we have one MSO with buttons inside and and a plain rectangle on the page:
the moment you group the MSO with the rectangle, the button will loose its target, if the target is an object state (of the same MSO).
That's my experience with InDesign CS5.5.
Ah! One thing left:
what will happen if you do not copy/paste an MSO but duplicate (alt + drag) an MSO with buttons inside?
See the following movie (hope the link will work. It's my first time with dropbox…):
@Bob – it seems it is the only way to get something like a button control from one MSO to another.
I stumbled over this just today so I had no time for testing.
So duplicating an MSO seems to be an option…
The example you see in the movie is a folio with PNG output saved as v20. Version 24 in this configuration is also doing fine.
I think we have to explore the new possibilities this will give us.
Though, I'm a little uneasy, because we leave the targets of the buttons inside the duplicated MSO in a very strange state:
Nevertheless, it could be an option for Single Issue Apps, because the folio is baked together with the app and could not change in a future version.
Further tests will follow…
And I'm looking for a way to address the target of a button inside a duplicated MSO directly by scripting, so that the target can be changed to quite another arbitrary MSO on the page without breaking the "feature".
I think this is a very good example for exploiting something like a bug or a not programmatically finished feature… :-)
P.S: Maybe someone, you?, should move that whole thread over to the DPS Forum?
Message was edited by: Laubender
@Bob – so let's go on with experimenting!
Here comes the real weird stuff:
a MSO that controls another MSO on a different page!!
What a day!
But to calm myself down: I still have to test that with different output formats and on the iPad…
By duplicating the one MSO from page 1 to page 2 with alt + drag, this seems possible now…
The target of the button inside the duplicated MSO of page 2 stays the same.
It points to the MSO on page 1!
Watch the second movie where I can proof this with the Content Viewer on my Mac:
At first you see page 1 of the article.
Then I switch over (down) to page 2.
Click the yellow button on the single MSO on that page (that switches the MSO on page 1 to state 2).
Then I switch back to page 1 (up), where the state of the one MSO has changed from state 1 to state 2.
I can already confirm that this is also working with the Content Viewer on the iPad.
But as I already said, if we can bake that feature into a Single Issue App,
possibly it will never break…
(And Now for Something Completely Different ;-) )
Until, of course,
I have to replace contents and therefore the app for a brand new version…
ouch...the grouping of buttons has just cost me quite a bit of time...what is a way to work around this? just to wait until the very last possible moment to create the buttons?
I have found something strange, if i have an object state with a rectangle and a text box, if i set the rectangle as the button the next state doesn't display correctly but if i set the text box as the object state then it does display correctly...
The second part was more of an observation than a question, I was trying to contribute to the "testing" When I convert the rectangle to the button the next state does not display correctly, but when I convert the text box to the button it works good....