Tab as a Key

@judith I'm not using the simulation function. I'm using triggers, layers, and hotspots to simulate what would happen when using the software.

The program is Oracle-based, and the users use Tab to advance to the next field.

OK, sorry - I know how to do it when you are capturing the action in the simulation.

Have you tried using a Text Entry trigger?

----

Insert Trigger

Action: Jump to slide

Slide: next

When: User presses a key      Key: Tab  (you don't type Tab, you tab in the box)

Object: Text Entry

----

I've used these steps, thanks for the suggestion.

The problem I have, is I have to continue tabbing (3 times) before the trigger is activated.

Is there a way to use Tab as a trigger, and have it to actually advance to the next slide, show a layer, or change a state?

Thanks,

-Nich

Hey Nick, 

Just did a quick test using the Tab key to advance to the next slide and it worked as expected with no extraneous Tab key pushes. Perhaps the extra Tab key pushes you're experiencing are from the accessibility box function? 

Hello everyone! I have the same issue with the Ctrl and Alt keys... in my project, I want to create a trigger when the learner presses just the "Ctrl" key, not "Ctrl+ some other key"

Same thing for "Alt" (just Alt, not Alt+something else)

Is this possible?

Thanks a million, I hope you all have a great day!

-Tom

Hey Tom!

Doesn't look like that's an option for now, but you're welcome to suggest it for future versions. 

Thanks!

This is for Brandon Driggers. He sent me a question by personal email, but I don't see his return email address.

Hi Brandon,

In Storyline, pressing Tab or Enter sends the focus to the Submit button. The Incorrect or Correct response comes up. The learner has to click Continue on the response message to continue. Most times, you continue to the next film cell.

Some options:

1.      When you record the simulation, do not tab between the fields – click in each field in the correct order and type the entry. This allows Storyline to capture the keystrokes from the learner without looking for a Submit each time.

2.      Keep the tabbing between the fields when you record, but realize that each time the user tabs, it activates the Submit button. This can be pretty annoying because the Incorrect or Correct response comes up each time you hit tab.

3.      You can record the simulation with the tabs, and set a trigger to move to the next scene when the control loses  focus.
Go to the slide containing the first field the learner enters. In the triggers for the simulation, add a trigger to jump to the next slide when the control (the entry field)  loses focus. You have to do this on each slide to keep the tab from activating the Submit button.

The Trigger Wizard should look like this:

Your triggers will look something like this. The arrow points at the trigger I added.

Let me know if this helps and if you need more details.

Good luck,

Judith

Thanks Judith!

HI Everyone,

I am having a similar problem.

I am using a trigger to hide a layer when the user presses the tab key. However when I do a slide preview, pressing the tab key not only hides the slide but it also highlights an option in the top bar. If I press tab more times it jumps around the slide navigation options.

Is there a way to prevent this from hapening? 

Hi James, 

It sounds like disabling the yellow accessibility box would resolve the highlighting issue. Have you given that a shot yet?

@Peter, after I disable the yellow accessibility box, will the Tab work as a trigger, or will it continue to cycle through the other parts of the screen (Menu and Resources)?

-Nich

Hi Nich, 

Good question. You can disable the yellow box for objects on your slide, but I don't see a way to disable it for menu items or player nav buttons. I did a quick test though, and it seems that if you build a trigger (to advance to the next slide, for example), that Storyline will respect that trigger first before any of the menu or player items become highlighted. 

Hi Peter,

I can't see a way to stop tab selecting the menu items either - which is quite supising really. Is there way to change the colour of the highlighting? I have looked through Colour and effects and couldn't see it as an option.

Or better yet - Is thee a way to turn off accessibility features altogether?

Hi James, 

Those would both have to be feature requests at this time. And good ones

Thanks Peter,

I'll send those ones through.

I need users to be able to tab through my simulation screeen WITHOUT Storyline going into Accessibility mode (or whatever it's called--it's a major annoyance, whatever you call it).

Is there a way to just turn off this yellow box tabbing functionality (you know what I mean) globally? If not, there definitely should be.

Hi JJ,

There is not a way to turn off the accessibility features, but as you'll see Peter recommended, you're welcome to submit it as a feature request. 

Hi Ashley,

We are still following the tutorial posted earlier in the forums to disable the accessibility feature for each object on every screen of our project. Just wanted to circle back to check if you have any updates on this feature request. Being able to disable this feature at a project (Story file) level would be a real boon.

Best,

Sam

Hi Sam,

Unfortunately I don't have information to share on future releases or versions and what features would be included. We'll keep everyone posted, and you may want to follow along with the Word of Mouth blog for updates!

Are there any updates for using the tab key as a trigger? 

Hey Jessica - Looks like Paul was helping you out here. I just wanted to link the two for anyone following along.

I am having the same issue with using the tab key as a trigger where it highlights objects in yellow.  Any updates for using the tab key as a trigger?

Hi Christine!

The yellow highlight box you're seeing is for keyboard navigation and tab order. What type of trigger are you trying to create? Is it possible to use another key besides the Tab key?