We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
I have just upgraded from 2017 to 2019.
I am working on an existing module that converted to 2019 when I saved.
I am previewing the module (before publishing).
On the hotspot questions, nothing appears where I click. I have checked the settings and all looks okay.
Can anyone point me in the right direction please? I really need the user to see where they have clicked.
Are you talking about a non-responsive or a responsive project?
This was totally my error ... I used Preview > HTML5 in Browser ... clicks didn't show on the hotspot questions. When I used SWF in Browser, the clicks did show as they should on the hotspot questions. Doh!
It's a little annoying that SWF in Browser opens in Edge and won't run. I have to open IE then copy the URL for it to run.
Edge doesn't support the Flash Player, and soon that will be the case for all desktop browsers except if you will keep with old versions. Next year is last year of Flash Player.
Do you continue to publish to SWF?
I will try to check the issue with hotspot questions for HTML output. Mostly I create custom hotspot questions because I don't like the limitations of the default type.
We publish to SCORM 1.2.
Both SWF and HTML output can be published to a SCO, that is not linked with my previous question.
Even a LMS is viewed in a browser. Can you prevent your learners to update their browsers, and/or to use an old version of a browser which will support SWF? You seemed to have missed the whole discussion about the death of SWF output which is along since almost two years.
Perhaps the screen shot below for our publish is more relevant.
So, am I correct in thinking, once Flash is gone (or before), we'll have to change the Output Format from SWF to HTML5?
Indeed, and that is not a one-click operation. I really fear 2019, when companies will suddenly discover that all old courses cannot be viewed anymore if the learners install a new version of their desktop browser. I tried to launch that warning as much as possible but earned more insults than thank you.