Skip to main content
Participant
April 19, 2018
Question

Rollover Slidelets behave differently when they appear later.

  • April 19, 2018
  • 1 reply
  • 268 views

I've got several slides in my non-responsive project that use rollover slidelets so that when users hover over different parts of a document screenshot, the title of that section appears on the slide, and when they click it, they're taken to the corresponding explanation slide. The image and slidelets are identical on each slide, and I've got two problems. The second one seems to stem from the solution to the first. 

1. The rollover area causes any animations to pause (but not my sound), leading to audio desync and weird entry animations. 
To solve this, I told captivate not to display the slidelet areas until after the animations are complete, so it won't interfere. However, that led to 

2. Now the slidelets always appear with a little white box with an "x" in the upper right hand corner, as pictured here: 

This only happens on slides where the rollover slidelets are not displayed for the entire slide. If they load with the slide, that X doesn't appear. 

Anyone know what causes this, and how I can get rid of that X? OR, is there a reasonable alternative to the rollover slidelets to accomplish this? I don't need HTML5 or responsiveness for this particular project. 

Thanks!

    This topic has been closed for replies.

    1 reply

    David Burnham HBA
    Inspiring
    April 19, 2018

    Unfortunately you cannot get rid of the X other than starting the slide at 0 seconds on the timeline which you already know.

    Going forward this is one of those objects that Captivate does not support in html5 output and although you say you don't need html5 for your project it could be problematic in the future if you are delivering on a "computer" when flash is no longer supported.


    Adobe really needs to look at adding rollover objects with click actions associated with them since current rollover captions and rollover images are that, rollovers only. Not all of us will design for the mobile platforms.

    Participant
    April 20, 2018

    I agree entirely. And looking for other answers on this particular error, it looks like this was first reported in 2011...might be time to patch this one, Adobe...

    RodWard
    Community Expert
    Community Expert
    April 21, 2018

    I also agree that there IS a place for rollovers, but when it comes to Rollover Slidelets the more likely outcome is going to be dropping the object from Captivate entirely because it is ONLY for SWF output.

    In fact, I would not be at all surprised to find that a future version of Captivate drops the SWF output as well and it becomes impossible to publish to any Flash output.