Skip to main content
Known Participant
April 2, 2013
Question

Text entry not working in LMS

  • April 2, 2013
  • 1 reply
  • 1567 views

We have a CP6 file with a text entry field that requires the user to type in "Copyright law" (not case-sensitive). The shortcut is "w."  It works fine in preview, and when the course is published to a folder on our web server, but when we import it into an LMS, it doesn't work and produces a failure caption.  We've tested it in both our LMSs and in SCORM Cloud, which says the manifest is fine, but it still doesn't work.

Does anybody have any suggestions?

Fortunately, this is a technique we rarely use, but I'd hate to have to change it and send out new versions.

Thanks!

This topic has been closed for replies.

1 reply

Known Participant
April 8, 2013

Replying to my own post here to elaborate on it.  I have tried publishing it outside the LMS, with reporting turned off, and the problem still occurs.

Captivate's default for a text entry field is "Enter."  This doesn't work with simulations - the user would not press enter in these circumstances.  A long time ago my Captivate teacher told me of a workaround in which you use the last character of the text entry (the character must be unique) as the shortcut.  So in the example "Copyright law" the shortcut would be "w", and in the example "=a" the shortcut would be "a".  This has always worked perfectly, but now it doesn't.  It works in the Captivate preview, but not when published.

This means we have to find every place we've used a text entry field (not many, fortunately), and change them.

Does anybody have any idea what's going on?

Steve Howard, ACP
Inspiring
April 8, 2013

Not sure what is going on, but you can use the Advanced Interaction window

to find all your interactions quickly - press F9 to view that window.

have you tried typing W vs w for the shortcut?

Steve

Known Participant
April 8, 2013

Yes, thanks, I'm very familiar with the Advanced Interaction - my favorite!

J

The problem is that it works perfectly in Captivate preview, but not when

it's published (with or without reporting). So presumably it's not an error

in the development.

And yes, I did try the capital - no luck, I'm afraid.

Thanks for the feedback.