Pause for user click missing after Seamless Tabbing fix.

Question

I am upgrading a project from Captivate 5.0 to 5.5. Two of the lessons that worked fine in 5.0 have problems in 5.5. Both lessons use the Tab key to move from field to field in a data row and then the Enter key to calculate at the end of the row. This worked fine in 5.0. In 5.5, pressing Tab caused jump to browser address window. I searched blog and found following solution to add:    so.addParam(seamlessTabbing:, :false:);        to the htm file generated when publishing the file. This is not a desirable solution for long term course maintenance, but it did work. Unfortunately a new problem then appeared. The project moved ahead without waiting for user input in the simulation exercises.
For slides with click boxes using Tab shortcut key and no other interactive objects, the movie just skipped ahead without waiting for user click. I would like the project to pause until the user presses the Tab key and then move to the next slide.  The properties for the click boxes are:
Action:
On success: Go to the next slide
Attempts: Infinite
Allow mouse click - yes
Shortcut: Tab
Options:
Captions: Failure only
Others: Pause for Success/Failure Captions and Pause project until user clicks
Timing:
Display for: Rest of slide
Appear after 0 seconds   (I have played around with this setting, but it does not seem to make a difference.)
For slides with Text Entry, the failure captions display before the user has a chance to input anything. Sometimes the captions flash several times at random. I would like the failure captions to only display when the user  enters an answer that does not match the stored answers.  The properties for the text entry boxes are:
General:
Default text: blank
Retain Text - checked
Validate User Input - checked
Var Associated: Text Entry Box ## (## changes from slide to slide)
On Focus Lost: No action
Action:
On Success: Go to the next slide
Attempts: Infinite
Shortcut: Tab
Options:
Captions: Failure only
Others: Pause for Success/Failure Captions
Timing:
Display For: Rest of slide
Appear after: 0.5 sec.
Pause After: 1 sec
Transition: No Transition
To test whether it was something I was doing in the editing, I went back to the original 5.0 version of the lesson and imported into 5.5 again and published without doing any editing. The lessons that worked fine in 5.0 did not work in 5.5. Then I tried replacing all the click boxes with new ones created in 5.5. That did not work. I tried adjusting the timing. That did not work. For the text entry boxes, I tried using Show Button, creating transparent button with Tab shortcut. That did not work. Several of these suggestions were ones that I found elsewhere in the Blog with similar but not identical problems. I never found a problem that combined the seamlessTabbing with the missed pauses.
I am puzzled and frustrated that these lessons that worked fine in 5.0 don't work in 5.5. Our primary edit is only to update the screen images and add a few new fields. I would often reposition an object on the slide, but not change its properties. Since most of the lessons are working fine in 5.5 and only these two that heavily use the Tab key are not working in 5.5. I don't really have the option of going back to 5.0. I need to put them in an aggregator and they all need to be the same version.
Is there a patch or a quick fix? Also, can the patch to the htm file be built in or is that what is causing the problem? For future course maintenance, it will be complicated to have to treat these two lessons specially. Also, we usually link to the swf file and not the htm file. Our users often use browsers other than Internet Explorer.
Any suggestions?   Thanks in advance.

Answer 1

It would seem Intego Virus Barrier X6 has an intermittent habit of putting the IP address of Apple TV into the Blocked Addresses list despite having checked the 'Trust Apple TV' box and inputting the address into the Trusted Addresses list. Over the course of less than a year this has occurred approximately 4 times to me. My last variation on getting to the root of the problem was to lock the settings with the padlock. I will monitor the situation and should it happen one more time will notify Intego of this 'bug'.