I've built a keyboard interaction that works fine when I preview the slide, and doesn't work when I preview the scene that the slide is in. Anyone have any clues?
Hi, Alex - There are some things we can check first to rule out some common issues: Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline to address erratic behavior. If issues persist, please feel free to share your file so we can take a look.
What are some of the issues that arise when working with files off the network? I've seen it mentioned several times that it's bad, but very little in the way of specifics.
The problematic page is 1.5. I've pasted the scene into its own project, and lost all the formatting when I did so, so it looks screwy.
1.6 is a page rebuilding the interactivity to compensate for the issues. It's not complete.
BTW - on slide 1.6, you'll see an "Incorrect" layer. It's simple enough to "code" the text to tell the user what button to click. I'd also like to code the "Continue" button to specify which layer to return to. I see no means to accomplish that. Is there a way? The only alternative is to provide 8 "Incorrect" layers, which is hardly efficient.
To answer your question regarding issues that arise when working with files off the network, it's hard to say specifically, because it can really cause anything odd to happen. Per our documentation, "Working on a network drive or an external (USB) drive can cause erratic behavior, such as file corruption, an inability to save changes, and loss of resources."
And I was able to check out your file (thanks for providing it), and in Preview, slide 1.5 appeared to function as intended, so can you clarify what issues you are seeing on your end? And regarding 1.6, if you want the continue button to get learners back to the same layer, you may want to uncheck 'hide other slide layers'. If issues persist, you are also welcome to submit a support case, and our team will be happy to explore these issues further. :)
Did slide 1.5 work as designed when you preview the whole project, rather than just that slide? That's the issue I'm having: the slide works fine when I only preview THE slide. If preview the scene, it doesn't work.
And thanks for the info on "hide other slide layers" - sometimes it's not clear what some of these functions control.
I tested 1.5 in Preview by itself, and then again when I Previewed the whole project, and it worked the same for me in both instances. Have you tried importing the file into a new file or running the repair for Storyline to address erratic behavior?
OK... I've followed the instructions for repair, checked my software versions, reinstalled Storyline (as a admin), copied the scene to a new file that I've saved to my HD, and I'm still having the exact same problem. More detail that might be useful: the first part of the interaction, where the user is supposed to enter "2", works. The second part, where the user is supposed to press "Enter" on his/her keyboard, doesn't.
Also, even the first part ("2") doesn't work unless I click somewhere in the screen first.
A number of other people in the building have had the same problem with it.
Same problem here, in a much simpler file. When previewing the scene, the first interaction works, the second one doesn't. If I chose to only preview the slide, both interactions work.
Just so you know, I've packaged the file and run it through tempshare, and see the problem there as well.
Hi, Alex -- Thank you for your response, and I tested the published output for the new test file you provided in the SCORM Cloud, and it appears to be working there, as well, so I am not sure where the issue you are seeing is occurring.
Here is what I saw: To progress from the 1st slide, I hit 'Next' in the bottom right corner, and then on the 2nd slide, I hit TAB to get the yellow box around the text, "This is the base layer. Click “1” on your keyboard to get to layer 1." I hit the number 1 key, and the text, "This is layer 1. Click “Enter” on your keyboard to go to layer 2." appeared. I then had to hit the TAB key a number of times until the yellow box appeared around the "This is layer 1. Click “Enter” on your keyboard to go to layer 2." text, and when it did, I hit the "Enter" key, and finally the text "This is layer 2" appeared.
I feel that since I am not able to replicate the issue, it might be best to Submit a Support Case for fresh perspective and further exploration of your issue.
Hi, Alex - Here is a little bit more information about the yellow box/TAB functionality that you saw when testing with the steps I outlined above. I am hopeful that our Support Team can assist you further, and please feel free to share your Case number and I'd be happy to follow along with their findings. :)
That works, but there's still a problem: I have to click in the screen before the keyboard commands can be used.
I imagine this is a focus issue, and I see no way to build a trigger to set focus.
I've built another way to do the interaction: I've put a numpad onscreen, and am having users click those buttons. I'm not sure this is worth troubling with anymore.
I was able to use the keyboard commands in your file with no issues. And did not have to click in the screen first. As Christie mentioned, you can submit your information to Support, and we can take a closer look.
One of my coworkers has pointed out to me that we occasionally will have users working from tablets, and that keyboard interactions wouldn't work for them. I've built the interaction with a number pad onscreen that users will use, and that interactivity works fine, thanks to the tip Christie provided about setting up the layer selections.
The fact that I couldn't get the program to do what I want is frustrating, but may not be worth exploring further, especially since you can't seem to replicate the problems I'm having. If someone wants to continue with it as a problem-solving exercise, I'll submit to Support. But my work-around solution is more appropriate for what we need anyway.
I do wish Storyline provided some more robust coding capabilities. I'm used to working in Authorware, where I could code anything.
18 Replies
Hi, Alex - There are some things we can check first to rule out some common issues: Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline to address erratic behavior. If issues persist, please feel free to share your file so we can take a look.
I just tried moving to local, with no change.
What are some of the issues that arise when working with files off the network? I've seen it mentioned several times that it's bad, but very little in the way of specifics.
The problematic page is 1.5. I've pasted the scene into its own project, and lost all the formatting when I did so, so it looks screwy.
1.6 is a page rebuilding the interactivity to compensate for the issues. It's not complete.
BTW - on slide 1.6, you'll see an "Incorrect" layer. It's simple enough to "code" the text to tell the user what button to click. I'd also like to code the "Continue" button to specify which layer to return to. I see no means to accomplish that. Is there a way? The only alternative is to provide 8 "Incorrect" layers, which is hardly efficient.
Hi, Alex --
To answer your question regarding issues that arise when working with files off the network, it's hard to say specifically, because it can really cause anything odd to happen. Per our documentation, "Working on a network drive or an external (USB) drive can cause erratic behavior, such as file corruption, an inability to save changes, and loss of resources."
And I was able to check out your file (thanks for providing it), and in Preview, slide 1.5 appeared to function as intended, so can you clarify what issues you are seeing on your end? And regarding 1.6, if you want the continue button to get learners back to the same layer, you may want to uncheck 'hide other slide layers'. If issues persist, you are also welcome to submit a support case, and our team will be happy to explore these issues further. :)
Christine - thanks for your response.
Did slide 1.5 work as designed when you preview the whole project, rather than just that slide? That's the issue I'm having: the slide works fine when I only preview THE slide. If preview the scene, it doesn't work.
And thanks for the info on "hide other slide layers" - sometimes it's not clear what some of these functions control.
Hi, Alex -
I tested 1.5 in Preview by itself, and then again when I Previewed the whole project, and it worked the same for me in both instances. Have you tried importing the file into a new file or running the repair for Storyline to address erratic behavior?
Hmm... guess I'll try a repair. Thanks again for your help.
Sure thing, Alex, and please update if the repair did the trick (or if you are still having issues, we'll see what more we can do to help)! :)
OK... I've followed the instructions for repair, checked my software versions, reinstalled Storyline (as a admin), copied the scene to a new file that I've saved to my HD, and I'm still having the exact same problem. More detail that might be useful: the first part of the interaction, where the user is supposed to enter "2", works. The second part, where the user is supposed to press "Enter" on his/her keyboard, doesn't.
Also, even the first part ("2") doesn't work unless I click somewhere in the screen first.
A number of other people in the building have had the same problem with it.
Same problem here, in a much simpler file. When previewing the scene, the first interaction works, the second one doesn't. If I chose to only preview the slide, both interactions work.
Just so you know, I've packaged the file and run it through tempshare, and see the problem there as well.
Hi, Alex -- Thank you for your response, and I tested the published output for the new test file you provided in the SCORM Cloud, and it appears to be working there, as well, so I am not sure where the issue you are seeing is occurring.
Here is what I saw: To progress from the 1st slide, I hit 'Next' in the bottom right corner, and then on the 2nd slide, I hit TAB to get the yellow box around the text, "This is the base layer. Click “1” on your keyboard to get to layer 1." I hit the number 1 key, and the text, "This is layer 1. Click “Enter” on your keyboard to go to layer 2." appeared. I then had to hit the TAB key a number of times until the yellow box appeared around the "This is layer 1. Click “Enter” on your keyboard to go to layer 2." text, and when it did, I hit the "Enter" key, and finally the text "This is layer 2" appeared.
I feel that since I am not able to replicate the issue, it might be best to Submit a Support Case for fresh perspective and further exploration of your issue.
Christie - thanks for having another look. I was unfamiliar with the TAB key function. Does that simply change focus?
When I perform the actions you described, the interaction works for me too. But I don't want users having to click the TAB key.
Alex,
Put your triggers on the slide layer. Right now you have them on the textbox, I am thinking that needs to have the focus for the trigger to work.
I attached the .story file. Let me know if that is what you were looking for.
Hi, Alex - Here is a little bit more information about the yellow box/TAB functionality that you saw when testing with the steps I outlined above. I am hopeful that our Support Team can assist you further, and please feel free to share your Case number and I'd be happy to follow along with their findings. :)
That works, but there's still a problem: I have to click in the screen before the keyboard commands can be used.
I imagine this is a focus issue, and I see no way to build a trigger to set focus.
I've built another way to do the interaction: I've put a numpad onscreen, and am having users click those buttons. I'm not sure this is worth troubling with anymore.
Thanks for your help.
Not sure how your project works but you could have them click something on the screen before they use the keys, this would give the window focus.
Hi Alex,
I was able to use the keyboard commands in your file with no issues. And did not have to click in the screen first. As Christie mentioned, you can submit your information to Support, and we can take a closer look.
One of my coworkers has pointed out to me that we occasionally will have users working from tablets, and that keyboard interactions wouldn't work for them. I've built the interaction with a number pad onscreen that users will use, and that interactivity works fine, thanks to the tip Christie provided about setting up the layer selections.
The fact that I couldn't get the program to do what I want is frustrating, but may not be worth exploring further, especially since you can't seem to replicate the problems I'm having. If someone wants to continue with it as a problem-solving exercise, I'll submit to Support. But my work-around solution is more appropriate for what we need anyway.
I do wish Storyline provided some more robust coding capabilities. I'm used to working in Authorware, where I could code anything.
This discussion is closed. You can start a new discussion or contact Articulate Support.