Notification
Newbie
1 posts
I am creating projects for testing users on a main frame product. I have no choice on the keyboard commands they have to use. It requires Tabs, Page Up, Page Down and Pause/Breaks. I am able to program them just fine. They work perfectly when I use Captivate 2017 and Preview them with the Project option . I have published them in both swf and html. Does something need to be on the web server that I might be missing? Is there code that needs to be updated or fixed? Please help.
Perplexed,
Dona Conn
I am creating projects for testing users on a main frame product. I have no choice on the keyboard commands they have to use. It requires Tabs, Page Up, Page Down and Pause/Breaks. I am able to program them just fine. They work perfectly when I use Captivate 2017 and Preview them with the Project option . I have published them in both swf and html. Does something need to be on the web server that I might be missing? Is there code that needs to be updated or fixed? Please help.
Perplexed,
Dona Conn
You must be logged in to post a comment.
- Most Recent
- Most Relevant
I have found a solution to my tabs not working problem. It is Java Script Code. It works.
Copy this code to the slide frame: Actions/On Enter/Executer JavaScript/Script Window
$(‘Text_Entry_Box_1‘).focus();
$(document).keydown(function (e) {
var keycode1 = (e.keyCode ? e.keyCode : e.which);
if (keycode1 == 0 || keycode1 == 9) {
e.preventDefault();
e.stopPropagation();
} });
or if using a Click Box
$(‘Click_Box_3‘).focus();
$(document).keydown(function (e) {
var keycode1 = (e.keyCode ? e.keyCode : e.which);
if (keycode1 == 0 || keycode1 == 9) {
e.preventDefault();
e.stopPropagation();
} });
On the actual Text Box or Click box do the following:
Select the Text Box – Choose Actions/On Success/Go to the next slide/ Shortcut is Tab(or what ever does not work) and On Focus Lost/ Go to next slide.
Hope this helps others that have to use this for now.
see this post
https://forums.adobe.com/message/10241266#10241266
this may be a solution to all of us – adobe needs to publish this into the code as an update IMHO
here is an Adobe 2019 sample does the same problem with html5 only. 1st screen works but rest do not.
