Skip to main content
danielb51742821
danielb51742821
Inspiring
September 28, 2017
Question

Smart Objects as buttons are not working as expected. Weird.

  • September 28, 2017
  • 1 reply
  • 2545 views

Hi,

CP 9.0.2.437.

I have a course with 4 smart shapes on every page used as buttons. Next, Back, Play/Pause and Open close TOC. It really total of 6 buttons, but the the two toggling buttons are placed on top of each other and using advanced actions they hide the undesired one for the obvious reason. The toggle buttons are placed on slide 2 and set to appear for the rest of the project "on top". The Next and Back buttons are placed on every slide individually due to some have pause buttons and others do not. Each button has 3 states - up, over and down.

The issue:

Each button does not react to a state change and is inactive for the top half of the button. Placing the mouse on the upper half does not display the hover state, and the button is not clickable. Only moving the mouse to the lower half works.

Any solutions or ideas?

    This topic has been closed for replies.

    1 reply

    Lilybiri
    Lilybiri
    Legend
    September 28, 2017

    Publishing to HTML5? Never put two interactive objects on top of each other in that case. Why do you not use a custom state to show the toggling? Have a look at:

    1 action = 5 Toggle Buttons - Captivate blog

    Do you have shadows on those shape buttons?

    danielb51742821
    danielb51742821Author
    Inspiring
    September 28, 2017

    Yes, publishing to html5. This method has always worked for me. In fact it worked for me in this project until I updated the shape/button images. The next and back buttons are not "stacked" and have the same behavior as the play/pause and TOC buttons. So I'm confident the stacking of some buttons is not the cause. I looked at your blog and at this point I'm not sure my pea-sized brain can get into that so late in this project. My buttons work as expected only if I click on the lower half of the shape/image/buttons. They work as expected when previewed in captivate but once published to html5 I get this behavior.

    Lilybiri
    Lilybiri
    Legend
    September 28, 2017

    I know that stacking can cause problems.


    What about my 'shadow' question?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices