Skip to main content
glow24583963
Participating Frequently
June 7, 2017
Answered

Overlapped timeline elements

  • June 7, 2017
  • 2 replies
  • 612 views

Hello,

Working in Captivate 10, non-responsive.

When I try to reorder items on the timeline, the often overlap. The element will still be listed on the left as a separate item, but is shown atop another item. (See screenshot.)

This isn't a huge disaster, and does correct itself on save and reopen. It certainly does make working with the timeline more difficult than it should be, though!

Any suggestions or workarounds here?

Thank you!

    This topic has been closed for replies.
    Correct answer Lilybiri

    That is an old bug, refreshing delay it is called. Mostly disappears when you navigate aways from the slide and come back, or when resetting the workspace. If you are using the newbie UI you only have Classic as workspace.

    2 replies

    glow24583963
    Participating Frequently
    June 7, 2017

    I should add that this behavior occurs only when I drag an item up or down on the timeline. Using the Arrange buttons on the ribbon does not appear to cause the overlap.

    Lilybiri
    Legend
    June 7, 2017

    Captivate has no ribbon, is not MS.

    It is a timeline refresh issue. Using the Arrange menu is not touching the timeline really, timeline is graphical.

    glow24583963
    Participating Frequently
    June 8, 2017

    Thank you, Lilybiri! It helps to know it's not just something I'm doing incorrectly.

    Lilybiri
    LilybiriCorrect answer
    Legend
    June 7, 2017

    That is an old bug, refreshing delay it is called. Mostly disappears when you navigate aways from the slide and come back, or when resetting the workspace. If you are using the newbie UI you only have Classic as workspace.

    Inspiring
    June 8, 2017

    Hi,

    Quick question: If this is an old bug, why is not fixed yet?

    Did someone report this problem?

    Piotr

    Lilybiri
    Legend
    June 8, 2017

    I reported it multiple times. Apparently not many users did the same, since it didn't get on the list for fixing.