A

Anonymous

Question

Exit button issue in Captivate 5

Forum|Forum|14 years ago
July 8, 2011
3 replies
15197 views

Hi,

This is regarding the exit button on the playback controls. I have been using Captivate from version 2. Recently, started using version 5. When I published my simulation, the exit button is not working as earlier. It is also not working from- web server(IIS, Apache), when opened as pop-up as well. In local too however not working. I tried in both IE 7 and Firefox latest version.

I have seen the response from Adobe on this issue on this forum. It was quite surprising; it did not talk about the solution at all;

What I am not sure about is -

1. Why the exit button was working earlier versions.. why is it not working in latest?

2. Why should when simple code like top.close(); works fine (when coded inside the Captivate)?

3. Why is Adobe not acknowledging the issue?

4. Why there is no working around provided in the forums for this issue?

Could anybody please help me understanding this problem? I am really frustrated.

Thanks.

This topic has been closed for replies.

J

jimitodd

Participant

Hi Guys

The exit button stops working when I click the "enable reporting for this project" check box.

It works fine in any browser I've tested it on and in the preview window, but as soon as I turn on reporting the exit button stops working and the project doesn't report to moodle.

I thought the problem was related to recently going to moodle 2 as it used to work.

But I think it's related to a patch update.

But it has stopped working in preview mode and when publishing to my desktop, which eliminates moodle and browser fault.

We are looking to upgrade to version 6 but if it won't close and report in moodle 2 whats the point.

We will be trialing Articulate Storyline in the new year to see if it reports any better.

That will be 6 licenses going to your rival as none of the fixes seem to work for me and adobe blame everything but themselves.

Thanks Jimi

K

kind_days15B9

Inspiring

Agreed, this is an exceedingly frustrating issue.

With SUPER all due respect to Rick (aka Captiv8r), I cannot accept that this is not a Captivate (6 or earlier) problem. Rick, I love you! You saved me so many times in the past! But this time, I am on a mission to make you reconsider that FAQ. The reason is quite simple, I have never experienced a problem with having a simple exit button that elegantly closes a lesson for the learner with any other rapid eLearning tool in the past.

Yes, Rick... you are correct that there are differences in how browsers behave but they are do behave in a predictable fashion (there are no mysteries) and proper coding (of an exit button) should account for the four major browser types. Yes, you are also correct in how the Captivate lesson opens its session but again, the browsers all work in very predictable ways. The problem is really Captivate and like many others, I need a solution.

Anyhow, rather than sleeping, I am hard at work to find a solution. I will find a solution, no matter how long it takes! Grrr....

I will post my findings in a day or two.

Seasons greetings, all!

Shawn

A

Anonymous

I must agree with some of you. There is something wrong if Captivate is the only authoring tool that does not offer a clean way of exiting a lesson.

Just as important to me is why isn't there a way of opening a lesson in a child browser window? On my LMS, the launch button page contains various details about the lesson. When the lesson is launched, it opens in the same window. When the lesson closes (which it does using similar code suggested by kwilli77 Thank BTW), the important launch information page is also lost. My manager finds this unacceptable and I too am looking for a way to launch a lesson in a child window.

shawninvancouver, the html code you published last week works nicely in forcing a lesson to launch in a child window. RE: http://forums.adobe.com/thread/1120709?tstart=0

**but** I can can confirm that I am experiencing the same problem. The consequence to using that redirector means that the LMS will not retain session information.

Anyone know why?

A

Anonymous

Not only frustrating but embarrassing to have invested in Adobe eLearning Suite, training for Captivate, and Skillport LMS only to find several suggested workrounds that I am able to try with my limited abilities do not actually work for me!

The only workround I have is to copy a few lines of html into the foot of the course .htm instructing the user to close the browser tab to end the course - but not the browser as a whole or the progress in the LMS will be lost. If companies like Adobe and Skillsoft want companies like ours to continue adopting e-learning it has to be made easier for people without programming or development expertise to use without extensive troubleshooting/trial & error.

There are several references to :

#10. The Exit button on the Playback Control doesn't close the Browser.. .

but this is really far from helpful.

This is not the only issue I have had in getting my simple Security Awareness Course to work just as I had it working on our Intranet.

It is finally published to the Skillport LMS but only at the expense of changing content as well as the Captivate project, and a very unsatisfactory and untidy ending of the course.

Captiv8r

Legend

Hi there

Indeed it is frustrating. Since the issue is with the browsers and not Captivate, how can you expect Adobe (or any other company for that matter) to change the behavior of all the browsers known to man?

Cheers... Rick

Helpful and Handy Links

Captivate Wish Form/Bug Reporting Form

Adobe Certified Captivate Training

SorcerStone Blog

Captivate eBooks

A

Anonymous

Rick - with the level of your experience I am a little taken aback by your reply. Yes I would expect any company providing a "feature" to get it working within a standard browser - or recommend changes to settings to try and get it to work. I know this is a forum and my issue is with Adobe and Microsoft IE not yourself. I am a big fan of Captivate and indeed use elearning suite 2.5 and will continue to use and recommend this and other Adobe products - although this is a small part of my job.

I believe we are in agreement that rather than wasting time getting this button to work that anyone struggling with this issue accepts it may not work and moves on! As I have. I did not want 6000 + employees globally, complaining that something we had published to the LMS did not work as expected - this would only distract from the content. As previously posted I have removed the button from the skin, included a final slide instructing the employee to close the tab but not the browser, and put a couple of lines within the html.

Incidentally what I have discovered from another post is that the "Hint" labels on the skin buttons can be modified to different languages. Great! Really useful for my course which is in several different languages.

Just to emphasise that the good stuff outweights the occasional negative.

Captiv8r

Legend

Welcome to our community

First, I suggest reading the link below.

Click here to read

And after you read the link, stop and ponder what may be different between what you are doing now as opposed to what you were doing earlier. My own guess is that you are opening and presenting the Captivate in a different manner than you were before.

Cheers... Rick

Helpful and Handy Links

Captivate Wish Form/Bug Reporting Form

Adobe Certified Captivate Training

SorcerStone Blog

Captivate eBooks

A

Anonymous

Hi Rick,

Thanks for the response.

Yes, I did visit the link you provided before I raised my questions.:-) However, that was not so helpful.

After investigating into the issue for a complete day, this is what I found.. I hope Adobe will address this issue in future releases. For everybody's benefit, I am providing the details here.

When a simulation published for no tracking (SCORM 1.2, 2004 and AICC), the exit button works fine, even when running in local. However, it does not work when you published the simulation for either SCORM 1.2/2004/AICC in all environments - Local, webserver, even when opened in a different window (as a popup). Definitely this was not the case with Captivate 2 or 3 (which I used extensively in the past)

The only place the simulation works when published for SCORM is - in LMS, that too not when imported SCORM zip file"as is" ( published by Captivate). Either you use LMS' default feature to open the simulation in a different window or use your own custom window opener file which opens the simulation in a different window. Another point to note is - response time for closing the simulation is little too much after clicking the exit button (when running in LMS, as mentioned earlier exit button does not work outside LMS).

As a industry standard practice, it is not desirable to restrict the functionality of exit button only to LMS environment. Of course, the SCORM content is finally destined to be hosted on LMS, but that doesn't mean when simulation is viewed from local/web server it should not function.

Hope this will help the people who will face the similar issue in future.

Thank you.