examples needed

I have not looked recently, but know there have been past demo videos and examples of some of the features of Captivate. I have my own projects but I would like to show a few leaders here on campus what is possible using just generic content or at least non-our college content.

They want to see examples of videos/lessons using the Table Of Contents feature, knowledge checks during the lesson, quizzes that require viewing of the content before attempting the quiz, and getting a certificate at the end of the video/lesson. I might end up create an example, but we are under a VERY short deadline (Nov2nd) so I wanted to reach out here first.

Even if I can get links to some videos of some of these features, that would be great. Interactive preferred but optional.

Thank you!

The post examples needed appeared first on eLearning.

Project created in Captivate 2017 and upgraded to 2019 publish html5 file when placed in LMS now I have to scroll.

I created a project in Captivate 2017 and I have since upgraded to 2019 version.  When I publish my file and place in the LMS, as I have in the past my project requires me to scroll now and before the project fit perfectly in the window.  What is different now?  Is there a setting I need to change?  Any help would be appreciated.

FYI- This is not a responsive project

-Thank you in advance.

 

The post Project created in Captivate 2017 and upgraded to 2019 publish html5 file when placed in LMS now I have to scroll. appeared first on eLearning.

Issue with Shared Actions (not disappearing when advancing/requires two clicks)

Hi everyone! First time poster here. I’m creating a curriculum for a client that wanted it created with Captivate. It’s a fish ID course, so each slide is a fish image. There’s a question mark at the bottom that, when clicked, opens the fish name. I made it a shared action so that when the user advances to the next slide, it is supposed to disappear.

It worked fine for one export, but now the actions apparently no longer work. Additionally, it requires two clicks to trigger the pop-up. I got these buttons working over two months ago at this point, and since it was my first time working with advanced actions, I can’t remember for the life of me what I did.  In the one screenshot of the Advanced Actions box, you’ll see that one setting is left blank. I don’t remember why that’s like that but it’s the same in the archived version of the project where the actions work correctly.

If anyone can advise, I’m happy to share a link to the project. It’s a massive file; every slide is an image so it’s 776.2 MB (even when saved as 150 dpi at 1280 x 720). I’ve included some screenshots that might be relevant. Looking forward to some answers!

The post Issue with Shared Actions (not disappearing when advancing/requires two clicks) appeared first on eLearning.

eLearning Livestream – Responsive Projects in Captivate 2019 | Oct 15, 12:00 EDT, 2018

The post eLearning Livestream – Responsive Projects in Captivate 2019 | Oct 15, 12:00 EDT, 2018 appeared first on eLearning.

Scrolling Marquee Sign

I was having some fun with creating one of those signs that scrolls messages across the display and thought I would share it with you.

As with all projects – there is usually more than one way to approach them but I hope this will simply provide some inspiration for some of your own projects.
Tackle it however you choose. Here is my rendition…

My little message board is made up of several states, a couple variables, and some buttons.

Image States
Of course, I had to create enough image states to represent all the updates in the display. My example has a display with a digital readout and total  of 33 states. Basically it was nothing more than doing a one-off of each of the letters so it did not take too long to create them. I did spend a little time trying to get what I thought was a decent glow on the letters for aesthetic purposes only.

Variables
I have two variables. One to track whether the display is on or off and one for helping to adjust the speed of the scrolling.

Buttons
I have four buttons. Two speed buttons – one to increase speed and one to decrease along with two buttons for turning the display on and off.

Function
Once started, the message will continue to scroll over and over until stopped. I wrestled a bit with immediately “powering off” the display and letting it finish the message and simply not repeat again. I decided to just stop it cold in order to reduce confusion over whether the button worked or not. The speed buttons will increase or decrease the speed of the scrolling by a hundredth of a second for each click of the respective arrow.

JavaScript
I decided to run with JavaScript on this, although I did make a version using advanced actions as well. I stayed with the JavaScript on this one because I felt it offered better control over the speed. The ‘Delay Next Action’ option is too clunky for me when timing is more critical. I will admit, though, that it was quicker in this case to simply create an advanced action with a ‘While’ condition to go to the next state.

On the green power button, the JavaScript itself is a simple repeating of a setTimeout function called scroll that changes the state of the display. The final setTimeout calls the first one as long as the variable for power is flagged. Here is an example of what they look like so you can see the pattern. I am sure there is a better way to script this but I can only work with what I know for the moment. We are also setting the go variable to 1, calling the scroll function,  and disabling the green button so that the scrolling is not initiated on top of itself.

function scroll() {
cp.changeState(“display”,”w”);
if (window.go==0) {
cp.changeState(“display”,”Normal”);
}
else if(window.go==1) {
setTimeout(scroll2, speed);
}
}

function scroll2() {
cp.changeState(“display”,”we”);
if (window.go==0) {
cp.changeState(“display”,”Normal”);
}
else if(window.go==1) {
setTimeout(scroll3, speed);
}
}

On the red power button we are simply changing the go variable to 0 and re-enabling the green button.

On the speed buttons, the code simply increases or decreases the speed variable by a value of 10. The setTimeout part of the javascript uses a value in milliseconds which means a value of 1000 represents 1 second. I have the default scrolling set for 100. It is worth noting that in order to decrease the speed of the scroll, I am actually increasing the speed variable while decreasing the speed variable in order to make it go faster.

If you have any questions about this please do not hesitate to post them.

I have included a working sample below.

Play

The post Scrolling Marquee Sign appeared first on eLearning.