All is linked with the obsession that all projects need to be responsive although only a minority of my clients ever asked for that type of projects, and even don't allow it in their company for security reasons. Moreover it should be 'easy' for new users (comparable to Rise) but I doubt that goal is reached.
Like Rod I have been very frustrated by the new version, based on losing so many features. As usual the Help documentation is 'frugal' and I logged several bugs in the text. Moreover there is not many other support available (blogs, videos, tutorials) by experts. A building which was created over two decades has just been erased completely: different terminology, UI (although the mother of that UI (which was XD) has now been abandoned). If this was a minor version of Captivate, and the professional version was really being supported further (like StoryLine and Rise) it would be less of a disaster. I started comparing Classic Captivate workflows with the New ones. It is hard for get them in the eLearning community, because I am always honest.
https://blog.lilybiri.com/bookmarking-in-captivate-classic-and-new-introduction
https://blog.lilybiri.com/static-bookmarks-in-new-captivate
ASAP I'll publish the same result in Captivate Classic... FYI this is supposed to be one of the few innovations except for the canned templates and blocks. Probably the term ' bookmark' has gotten another meaning in the new version. It does better than Classic to use it as trigger for an event action, but as bookmark it is not.
3
Replies
AdChoices