Skip navigation
Currently Being Moderated

buttons in object states

Feb 14, 2013 4:59 AM

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?

 
Replies
  • Currently Being Moderated
    Feb 14, 2013 5:17 AM   in reply to hooplife

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 14, 2013 1:57 PM   in reply to hooplife

    I've created MSO with 40 states and copy/pasted them.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 2:45 AM   in reply to Bob Levine

    @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.

     

    Arg!

     

    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.

     

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 5:03 AM   in reply to Laubender

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 5:30 AM   in reply to Bob Levine

    @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…):

     

    https://www.dropbox.com/s/et30rl16ueq5g04/MSO_controlsOTHER_MSO_HighRe s.mov?n=49486054

     

    Have fun!
    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 6:15 AM   in reply to Laubender

    Interesting...I can say I've never tried any of that so I wouldn't know

    about it.

     

    I always copy/paste MSOs from one file or page to another and it's

    always fine.

     

    And the movie worked fine.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 6:51 AM   in reply to Bob Levine

    @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:

     

     

    ButtonInDuplicatedMSO_png8.png

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 6:54 AM   in reply to Laubender

    Ouch. That would appear to be a problem that could blow up at a very bad

    time.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 7:14 AM   in reply to Bob Levine

    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… :-)

     

    Uwe

     

    P.S: Maybe someone, you?, should move that whole thread over to the DPS Forum?

     

    Message was edited by: Laubender

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 9:11 AM   in reply to Bob Levine

    @Bob – so let's go on with experimenting!

     

    Here comes the real weird stuff:
    a MSO that controls another MSO on a different page!!

     

    https://www.dropbox.com/s/s0wvlfnypk1i7gc/MSO_controls_OTHER_MSO_on_OT HER_PAGE_HighRes1.mov?n=49486054

     

    What a day!

     

    But to calm myself down: I still have to test that with different output formats and on the iPad…

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 9:25 AM   in reply to Laubender

    A first test with "Preview On Device" is showing that the PNG folio is working as expected!
    (iPad 3).

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 9:49 AM   in reply to Laubender

    Another InDesign limitation. If you have a button on a spread it will

    only control an MSO on that spread, as far I know.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 10:27 AM   in reply to Bob Levine

    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.

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 10:39 AM   in reply to Laubender

    Interesting, but I can't help but worry about it breaking.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 15, 2013 10:50 AM   in reply to Bob Levine

    Me too…

     

    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…

     

    Uwe

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 25, 2013 5:08 AM   in reply to hooplife

    Waiting until you have a final structure for MSOs is the only way to get buttons in the MSO to operate properly. I'm having trouble figuring out what the second part of your question.

     

    Bob

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points