I set up a (quite) simple presentation where users can navigate using keyboard (Page Up/Down and B keys, which are actually presentation remote keys).
As those keys are common to all slides, I put the triggers on Slide Master.
Slides are quite short, around 6 seconds. Some are just still pictures.
Now, for some reason, on some slides, if you wait for a few seconds, you won't be able to use keyboard to move forth or back. This won't happen on most of them.
I made some tests and it looks like a kind of "focus" problem : if a object disappears from the base layer, SL won't listen to key presses anymore. If you click anywhere on the slide, you can navigate with keys again (but the point is to use remote NOT mouse !).
For some reason, it still works if an object appears on base layer !
Did anyone ever get an update on this issue. I have a trigger on the master slide base layer to go to the next slide when the user presses the right arrow key. It works for 2 slides, but then it loses focus. If you click on the window the story is running in it will work again, but again for only 2 slides. Seem like a big for users with disabilities if they are not able to progress through a file without the mouse
Thanks Pierre for sharing that here - I'll get a note in the existing issue to have our team take a look at this for if the fix is able to be ported back to Storyline 2. The good news is if it's fixed in Storyline 360 that should carry over into Storyline 3 when released.
13 Replies
On one of the blocking slides, if I delete the top picture, problem is gone !
There's nothing special about it, no animation.
Case submitted!
Hi Pierre!
Thanks for mentioning that you have reached out to support. I see your case (00439743) and you should be hearing from someone soon.
I made some tests and it looks like a kind of "focus" problem : if a object disappears from the base layer, SL won't listen to key presses anymore. If you click anywhere on the slide, you can navigate with keys again (but the point is to use remote NOT mouse !).
For some reason, it still works if an object appears on base layer !
I have shared your additional comments in your case as well as it looks as if they are in testing now.
Thanks Leslie !
Here are two simple examples :
This will work because the top object remains till the end.
This won't work because the rectangle disappears! Keys stop responding after rectangle is gone!
Did anyone ever get an update on this issue. I have a trigger on the master slide base layer to go to the next slide when the user presses the right arrow key. It works for 2 slides, but then it loses focus. If you click on the window the story is running in it will work again, but again for only 2 slides. Seem like a big for users with disabilities if they are not able to progress through a file without the mouse
Hi, Reece.
No update from SL team on this issue.
Luckily I managed to find a workaround, a SWF that will set focus on the animation.
I forwarded this to the team hoping they would find inspiration for a fix but I got no news since.
Feel free to use this workaround... at your own risk ! (not heavily tested). Just put it on the timeline of blocking slide.
Don't know if this will work on master though.
Let us know...
Of wourse, a fix would be a better solution in any way.
Hi Reece and Pierre! Yes, this issue is still in the hands of our QA Team. I have no update to provide.
Pierre - I appreciate you sharing your workaround :)
Wow, that works! Do you happen to have the .fla file for the swf? Is it just a blank .swf or is there actionscript in it.
Good news Reece!
Here's the AS3 code :
var timer:Timer = new Timer(1000, 2);
timer.addEventListener(TimerEvent.TIMER, focus);
timer.start();
function focus(e:Event):void{
stage.focus=stage;
}
It seems this issue is fixed (at last!) in SL360 (Flash output as well). Maybe we could get a fix as well for SL2 in the next update ?
Thanks Pierre for sharing that here - I'll get a note in the existing issue to have our team take a look at this for if the fix is able to be ported back to Storyline 2. The good news is if it's fixed in Storyline 360 that should carry over into Storyline 3 when released.
This discussion is closed. You can start a new discussion or contact Articulate Support.