Unable to install Captivate 2019 update 11.0.1

I’m running Build version 11.0.0.243 and am unable to install the update to 11.0.1.

When I run the updater, I get an Error Code 131 – “Please save your work and close the following programs for all logged in users, then click “Continue”: – Adobe Captivate (Error Code 131).

I’m running it as Administrator and have no other applications running.

Is there an Updater preferences file or something that I can rename or delete? I saw that was a solution for a similar problem with an earlier version of Captivate.

The post Unable to install Captivate 2019 update 11.0.1 appeared first on eLearning.

Strange Issue

Hello,

I was editing some sound files, narration specifically, in my latest project. I changed up the timing a bit and pulled up a “From this Slide” preview and the sound file was duplicated meaning the track would start where I had it placed originally then a second track would start to play at the time point that I moved it to.  I poured through the audio folder in the Library to see if I had duplicated files and I did not. I decided to delete the track out of the library and import it again. Then, just to see if I was on the right track, I ran the preview again and the narration sound file was still there. I searched for the track every way I could think of and could not find it in Captivate.

Out of desperation I decided to just delete all of the sound files from the the Library in hopes I’d somehow “scoop up” the one I was after. After doing so, I launched the preview again and several of the slides STILL have the narration on there. I then launched a preview in HTML5 format and the sound is gone. What is going on? It’s behaving as if there’s a cache file the previewing is drawing off of.

Any thoughts?

Brett Koranda

The post Strange Issue appeared first on eLearning.

Captivate 2019 files backwards compatible with 2017 files?

My company bought 2017 when it came out and I subsequently created themes and templates using that version. We’ve recently hired a contractor to help me with a project, and my IT dept. is saying Adobe will no longer allow us to purchase the 2017 version, and that we must get version 2019 for the contractor.

The contractor and I will be working on and editing the same files over a long period of time.

I am assuming the contractor will be able to open my 2017 files and apply the themes.

However, when the contractor saves their files in 2019, will I be able to open them in 2017 without any issues?

More specifically, will the project open correctly with no changes to fonts, interactions, elements, timings, etc.?

The post Captivate 2019 files backwards compatible with 2017 files? appeared first on eLearning.

Object audio failing to execute

Hi there,

Recently I have begun adding recorded audio to multi-state objects. I like this approach as I find it much more organised when there are a lot of objects on a slide. I find that the timeline can become very tricky to keep track of some times. However, sometimes for some unbeknownst reason the attached audio does not play in the export. If you have time,please have a look at my attached video in which I try to (as clearly as I can) outline the exact issue. Any help or ideas would be most appreciated as I have been pulling my hair out for a few days with this issue.

Many thanks!

Fergus

The post Object audio failing to execute appeared first on eLearning.

Using Text Entry Boxes: Basics

Intro

There are several reasons why I felt need for this article. I watched a basic tutorial recently skipping a very important step and including a cumbersome unnecessary workflow. Lot of questions appear on social media including Adobe forums and eLearning community. Posts about Text Entry Boxes in my blog and were written for older versions. Time to translate everything to the most recent version (11.0.1.266 today) and for HTML output because there are minor differences. This article is very basic, meant for newbies, eventually for more advanced developers to refresh their memory.

Validated or Not

Text Entry Boxes are Interactive Objects. It may be a bit confusing since CP8 (change of UI) that you have to find them under the Text Button, not on the Interactions button. There are a couple of ways to recognize interactive objets:

  • Their timeline (when not selected) is green
  • In the Properties panel you have a tab Actions, allowing to trigger one or two actions
  • You can turn on Reporting in the Actions tab. A score attached to the objet (default = 1pt) can be added to the total quiz score.

Text Entry Boxes allow to let the learner enter text, which will be stored in an associated variable. This means that it the value can be used later on. It is one of the two interactive objects that will be automatically inserted when creating a software simultaion in Training or Assessment mode (the other object is the click box), whenever the learner is required to fill in a field. In Captivate tthe only other ways to allow learners to put in text is by using the Notes or the Scrolling Text Interactions.

Text Entry Boxes can be used in two ways:.

Not Validated

This is the default setup, learner can enter whatever he wants,  any entry is considered to be correct.

However you can restrain the characters that may be used by clicking the More Options button, and you can set the required number of characters as well. If you activate the option ‘Auto Submit’ it will be submitted when the lenght of the entry has been reached. You don’t need the Submit button in that case, can drag it out to the scratch area. If you don’t activate anything in More Options, all characters (numeric as well) will be accepted but that option will (strangely) not be checked.

Let us look at the Actions tab. As with quiz and Knowledge check slides, you have a Success action and – in case of limited attempts – a Last Attempt action. That is a bit confusing, because any answer is considered to be correct for a non-validated Text Entry Box.  and the cause for a question that pops up sometimes in the forums. There is only a Success event, which means the Success action will be done all the time. Look at an example from a recent question:

I offer 3 attempts to fill in a TEB, but it is only possible to enter once, the playhead moves on after the first submission‘.

Default Success action is set to Continue for a TEB.  This action will be executed after the first attempt, playhead moves on indeed. To avoid that, you could change the Success action to ‘No action’. Result: user will have to fill in the field three times, after the third submission the Last Attempt action will be done. Maybe not what you want?  An easy solution is to add a custom button ‘Next’ to move to the next slide for users who do not want to fill in the field 3 times.

There is no built-in functionality to check if anything has been typed in the field when the Submit button is clicked. You can use the workflow described in this post if you don’t want to end up with an empty variable.

Option ‘Reporting’ will be dimmed for a non-validated TEB, which is logical.
Sometimes ignored, but worth mentioning: if you expect to have a long text to be entered, please check the option ‘Show Scrollbar’. You can see it activated in the most recent screenshot.
The shortcut key is Enter, which is pretty common to confirm an entry in a form field. You can change it to TAB if you have mulltiple TEB’s on the slide.

Validated

A Text Entry Box is validated when you check that option.  WIth the selected TEB a HUD will appear to enter the possible correct answers using the + button.  It is recommended to put the By default the option ‘Case sensitive’ is not checked, but I did so in this screenshot:

Tip: you can resize the TEB, it is not necessary to put the longest entry on top as is the case for FIB quest

Because you have defined correct answers, the TEB has now two events: the Success event, and the Failure event if you have a limited number of attempts. Success action is only happening if a correct answer is given, the Last Attempt action after the last attempt if that was still a failure. Be sure to turn on the Success and Failure captions. There is no Retry message as you can have for quiz slides, nor multiple Failure messages. I have a workaround for that, but that is outside of the scope of this basic post.

A validated TEB can be scored, the score can be added to the Quiz total (will appear in the Advanced Interaction panel) and be reported. As I mentioned before, when creating a Software Simulation in Training or Assessment mode, you will see that reporting is turned on automatically.

Typical use case for validated TEB’s: use multiple TEB’s to create a custom Fill-in-the-Blank question, if you want to have each blank field to be scored individually. That is not possible with the default FIB quiz slide.

Associated Variable

A Text Entry Box needs a, associated variable to be functional. That is the reason why a generic variable is created automatically. It has the same name as the Text Entry Box, which is a bit confusing because the general ‘law’ in Captivate is never to reuse a name for a second item. However there is a very easy workflow to create and associate immediately a user variable with a more significant name. No need at all to open the Variables dialog box and create that user variable (as you can see in other tutorials). Follow these steps, after having inserted the Text Entry Box (validated or not):

  1. Click the X button next to the Variable field which currently contains the generic variable (in the screenshot it is “Text_Entry_Box_3”
  2. Type a name for the user variable. It will be created and associated with the TEB. In the screenshot: “v_name”
You can verify (not necessary) in the Variables dialog box. The original variable with the generic name is still there, but as you can see in the following image, no longer in use. If you are in spring cleaning mode you can safely delete it.

Displaying Variable

This is not specific for a TEB variable, but for all variables. More details in this post.

Do not type in the variable in a text container with the surrounding $$ but use the X button in the Properties panel (consistent, also X button). Not only do you avoid typos that way (variables are case sensitive) but you can check the number of characters that will be displayed. Default length is 50, but that may be too low, in which case you have to edit this length.

The post Using Text Entry Boxes: Basics appeared first on eLearning.

Problems with Captivate HTML5 output in Chrome

I am using Captivate 2017 (10.0.1.285) and publishing as scalable HTML5. It runs perfect everytime in IE. However I get random problems when run in Google Chrome and Edge. The problems always involve smartobjects. Sometimes they won’t display or will display the background but not the text (The text has a variable). It is very frustrating because it does not happen all the time. Has anyone else had issues with smartobjects in Chrome and/or Edge?

The post Problems with Captivate HTML5 output in Chrome appeared first on eLearning.