Double click does not work in published simulation. html5

[sexy_posh]

I published my simulation both as html5 and swf.  In the publish folder, I double-clicked the index.html to launch the elearning and then play through it. The issue I noticed is that double clicked did not work in some of my slides.

If I launched the elearning using the .htm extension from the published folder, the simulation accepted the double click action.

[RodWard]

Double-click can be a little tricky to implement in a browser-based environment because if there is any action available to a single click in the same instance then the browser will execute that action at the first click of the double-click.  Essentially, it doesn't wait to see if there's a second click following up close behind.

That's why we built the Double-Click Delay option into CpExtra:

CpExtra Behavior | Infosemantics Pty Ltd

[BDuckWorks]

You're double clicking an html file to launch the course?

What does the url look like when it's launched?

If it starts with "file:///C:/" you're playing the file locally in your browser, and some functionality won't work.

You'll likely get no warnings, no errors, it just won't work correctly. I'm not sure if this is the case with a double-click event, but it may be.

For best results, you should upload your files to a webserver, or test in a dev area of your LMS.

[sexy_posh]

Yes, I am launching the course from a published folder.

what I meant of double-click, is the action simulation which I recorded in the slides. For example, the text caption instruction will say "Double click on Incidents".   I am sure that the selected 'double click' check box in the clickbox properties:

It does not work when I launch the project in html5 or using .index html

[sexy_posh]

Hi BduckWorks,

What other functions will not work when launching the simulation from a  my local browser  besides the double-click action?

And yes, the url look like this  "file:///C:/Users/......." .

thank you

[BDuckWorks]

Most of what I've seen that fails are links to external media, YouTube videos for example, won't function properly in the widget/interaction if the course is played locally.

There are cases where JavaScript commands have failed, or are not seeing the correct path to function, when played locally.

The other common problem, when publishing to SWF, is that flash global security may not have permission to use the folder. Best case, this will cause a warning in your browser; worst case: the course fails completely without warning or error.

Most of the time these errors are of little concern for course developers, but when your asking for customer approval of course content, or hoping an executive will authorize further funding or course development resources; that can be disastrous.

If you can get your IT department to provide space on a web server for course testing, and get in the habit of publishing to that location to test your Cp projects, then you'll have a consistent platform to ensure that your projects are working. When you run into issues while publishing your 14th or 15th course, and are testing the same way the others have worked, you have some assurance that the issues you are experiencing during testing are isolated to your Cp project. You can look at the new features you've added to this course, or review SCORM settings used in earlier courses, and be confident in your troubleshooting approach.

It's a little more work for each cycle of publish, review & revise; as you need to build the files from Cp, move them to the server, build a new URL (if you changed the filename) and test it; but it will be a better experience for your team and your users.