Skip to main content
S
sfdjklsdadfjkasldj
Inspiring
May 25, 2016
Answered

Captivate 9 Bizarre Timeline Behavior - Multiple Items on Same Row

  • May 25, 2016
  • 2 replies
  • 831 views

I am migrating a Captivate 7 program into Captivate 9.

I opened Captivate 9

I opened the Captivate 7 version

Everything worked beautifully.

Suddenly the timeline is behaving badly.

Now when I try to change the stacking order, multiple objects are appearing on the same row. Some rows are empty.

Has anyone seen this? I've included a screen shot.

Items 1, 2, 3 multiple items on the same row

Item 4, rows are empty.

Can anyone provide advice?

This topic has been closed for replies.
Correct answer sfdjklsdadfjkasldj

Thanks Lieve. I tried everything except resetting the workspace (didn't think of that!). Finally decided the project was corrupt (it wasn't happening in any other projects).

I ended up creating a new project and copying slides to the new project. It worked fine after that.

Grr..... an hour lost

2 replies

S
sfdjklsdadfjkasldjAuthorCorrect answer
Inspiring
May 25, 2016

Thanks Lieve. I tried everything except resetting the workspace (didn't think of that!). Finally decided the project was corrupt (it wasn't happening in any other projects).

I ended up creating a new project and copying slides to the new project. It worked fine after that.

Grr..... an hour lost

Lilybiri
Lilybiri
Legend
May 25, 2016

Timeline going crazy, happens sometimes.


Did you try:

  • to navigate to another slide and come back to this slide (mostly helps)
  • to reset the workspace - if first solution doesn't help?
  • to restart Captivate if second solution gives no result?
  • to clear the cache?
  • to restart your system?
AP_AW
AP_AW
Inspiring
July 14, 2016

This has started happening to the first slide in my project as well. Trying one of the solutions you've provided make the timeline look ok but when you try to change a layer things go awry.

Lilybiri
Lilybiri
Legend
July 14, 2016

Time to restart the system, and I would be careful because this could be the start of a corrupted project.

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