Copy link to clipboard
Copied
Hello,
I have a software simulation project and I have built my own navigation bar on the master slide.
Everything on the master slide disappears for about a half second when the project moves to the next slide.
Does anyone have an idea how I can take care of this issue?
Thanks for any help!
Copy link to clipboard
Copied
Can you check the styles in the Object Style Manager for shapes (since you put the buttons on the master slide, they have to be shape buttons)? Maybe by default they have a Transition, a Fade out effect?
Copy link to clipboard
Copied
@Lilybiri
Hello,
I did some debugging and now I think I can refine the problem a little bit:
Copy link to clipboard
Copied
And one more point:
Copy link to clipboard
Copied
Did you check the object styles? Is this a project created originally in this version, or did you upgrade anything? In previous versions Transitions were default for a lot of objects, that is the reason I asked to check the styles.
Slide transitions are not supported for HTML output, that cannot be the reason.
Since it happens always on the same slides, you really should check the Transition possibility for the objects. On Slides you find it in the Timing properties.
Copy link to clipboard
Copied
The object style does not have a transition.
I took the original file that was produced when I did the software simulation (with both system and 'normal' audio) and with copy and paste, I put the same smart shape on the first ten slides. That was the only change from the original software simulation recording. So it is the same shape, same location, same style. The shape is timed to show for the entire slide. Between slides 4 and 5 and 6 and 7 , the shape disappears for a half second. By the other transitions from one slide to another it doesn't.
Copy link to clipboard
Copied
I would never put the same shape on 10 slides in sequence, but time it for the rest of the project on the first slide, and hide it with the On Enter action on the 11th slide. Is there any reason why you prefer 10 objects instead of one? You have to check the option 'Always on top' of course. If the course can be visited in a non-linear way or back button can be used, you'll need to show it with the On Enter action on each slide. You select the 10 slides and create that action, which can be a simple action.
Personally I never did see this issue at all, have flickering issues when a shape has an effect, but not when it is simply on a slide or a master slide. Since I am a big fan of shapes, it is a bit puzzling that I never encountered this.
Forgot to ask about the exact version you are using?
Copy link to clipboard
Copied
I am using Captivate 9.
The solution with putting the item on the first slide, setting it to show for the rest of the project, and hiding and showing it on slide enter works.
The same item on 10 consecutive slides was purely done as a test to see if smart shapes that are NOT set for the rest of the project disappear for a split second the project moves to the next slide. They do, unfortunately. I wanted to use the same object on each slide to exclude the possibility that the reason they disappear on some slides and not others was due to the fact that they are in some way different.
Copy link to clipboard
Copied
Exact number, please, there were some bugs in the first release. Are you on 9.0.1.320?
Is this 'shape' a button functioning as Next button?
Copy link to clipboard
Copied
9.0.1.320.
No, that I am testing with is not a button - just a shape.
Copy link to clipboard
Copied
Sorry, I mean the shape that I am using for testing is not a button - just a shape.
Copy link to clipboard
Copied
The initial 'blink' of the object is probably due to the fact that in HTML5 output the objects don't get loaded until you get to the slide and that will take a split second or so (depending on the size of the image or object)..
Objects that are loaded on earlier slides and timed for rest of project will only need to be loaded on the first slide where they appear and will therefore not 'blink' on later slides.
SWF projects don't suffer as much from this same issue because they use a preloading strategy. HTML5 projects don't use as much internal caching because mobile devices typically are memory starved, so they opt more for downloading objects only when they are needed. This means you don't usually get the same seamless user experience with HTML5 projects.
Copy link to clipboard
Copied
Rod - thanks for this. It helped me solve my mystery issue.