use the TAB key in a training simulation

[sybmathics]

Hi everybody,

Our company trains people in the use of keyboard keys as a replacement for mouse clicks. To this end I create instructional captivate demonstration and training simulation movies. When I record a Tab key in a training simulation the result is not as hoped for. For instance, instead of selecting the next object on a Powerpoint slide, the focus jumps to the pause-button on the VCR controls. Is there a way of escaping this standard Tab function?

I hope you understand my problem. Any help is greatly appreciated

Greets,

Sybolt

[Captiv8r]

Hi Sybolt and welcome to our community

When you recorded, were Click Box objects added? In other words, did the recording occur in such a manner as the user is expected to click or press keys to make it progress from screen to screen? If so, then you recorded in Simulation mode and Click Box objects exist.

If this is the case, did you modify the Click Box in any way? I ask, because you have the ability to specify something called a shortcut key that, when pressed by your user, causes the click box to be activated the same as a mouse click would have.

Sincerely... Rick

[sybmathics]

Yes, I record in simulation mode and yes the user is expected to use the keyboard instead of a mousclick to progress to the next slide and yes there are shortcuts attached tot the clickboxes. for instance a short cut is TAB.

But when a user uses the TAB, the focus jumps to the rewind button in vcr controls. the simulation doesn't respond in the correct way. So my question is: how do I escape the VCR controls.

[BigDaddyNAZ2006]

Greeting Sybolt,

I too have had this same issue. Most of my simulations use text-entry fields where the end-user must hit the "Tab" key to advance to the next field.

The only way I have found to avoid this from happening is remove the playbar. I have created my own buttons for "back", "exit", and "next".

In my simulations where the end-user is on the page where they must enter text and press the tab key, I just remove the buttons. This forces them to follow the interaction and not jump forward to the next screen using the "next" button.

HTH

Jim