Skip to main content
K
Kris Thayer
Known Participant
February 3, 2016
Question

Menu/playbar offset when running Captivate course in a web-object of another course

  • February 3, 2016
  • 1 reply
  • 332 views

Hi, we are creating a course shell with Captivate 9 that includes many elements including a few tutorials that display another Captivate 9 published course in a web-object on a screen in the course shell.

After a user plays through the tutorial the first time, closes the master course, and then reopens in the LMS, the cursor response is offset by about 1 inch from the object. For example, if I hover the mouse cursor over a menu item, the actual menu item that highlights is about 1 inch above where the cursor is placed. In the playbar, I can't even click any of the buttons because it seems that the cursor is about 1 inch off and the actual hotspot ends up being below the course window.

Any ideas?

Thanks,

Kris

    This topic has been closed for replies.

    1 reply

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    February 4, 2016

    I can't recall seeing this issue before.  But just for a test, try hiding the slides that contain the other Captivate projects in web objects and republish to test if you get the same issue.  If not, then the issue is due to nesting Captivate projects inside each other I would say.

    K
    Kris ThayerAuthor
    Known Participant
    February 4, 2016

    Hi Rod, thanks for your quick reply and suggestion. I'm not sure how this would help because the slides with the other projects are the problem. This does not occur in the master course shell, only in the web objects/Captivate tutorials that we interact with. If we can't nest Captivate projects inside of each other, how else can we use self-contained Captivate projects within other Captivate projects? They want one screen to contain one tutorial within the course shell. They don't want sub-navigation within the master course.

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    February 4, 2016

    OK.  Trying to nest one Captivate project inside another very often results in issues, so I'm not surprised that you encountered some as well.  That's why I originally suggested taking them out of the picture.

    In your case you have it in a web object and it's causing issues, but at other times Captivate developers have inserted a published SWF from a Captivate project as an animation in another Captivate project slide and that can also result in issues because the code in the child object conflicts with the code in the parent object at run-time, especially if you happen to be using skins and playbars.

    My feeling is that when you hover over the menu items the code may be designed to take its reference point from the top left of the browser window, but not expecting itself to be sitting INSIDE an iframe on another window.  So the offset may be about the same distance as the iframe corner is from the actual browser corner?

    Does this perhaps look like what is happening to you?

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