Articulate members, please help, I have a project where multiple slides have a base layer and a hint layer. Most of the slides work fine but other slides will display the hint layer upon entering the slide and not when the user clicks outside of the Hotspot. Any assistance is greatly appreciated, it's driving me nuts. This occurs when previewing or publishing.
Thanks so much, Walt. When I get to the last slide 1.6 in preview the Hint slide layer displays. This happens on other slides and I just put a few slides together that were displaying this behavior. I know a few slides don't have hint layers.
Jürgen, I don't think that's the issue when the slide advances the hint layer is visible as soon as the slide advances- When I delete the layer and the hint trigger, it works fine. When I add back the hint layer and republish the layer is visible again without doing anything.
@Eric, I am still having the same issues even when recreating slides - I do not think this is the fix. I would love to do a screen share, if possible, with a staff member.
All- even recreating a new project and inserting new slides and inserting elements (not copy/paste) produces the same error of the hint layer displaying prior to the user clicking outside of the rectangle area. #frustrated
The “When user clicks” trigger is fired on mouse up, not on mouse down. So, if you click the mouse button down and hold it, nothing happens; once you unclick the mouse button, the trigger fires. That’s pretty standard web behavior—no issue there.
And in our case, that wouldn’t be an issue if the learner was using the NEXT button to advance the course; they’re clicking in the player, not on the slide. However, on some of our slides, the learner clicks an object on the slide to advance to the next slide. This is where our issue comes in: in our case, when we have two slides in a row that have the “When the user clicks outside [whatever object]” trigger, the second slide registers the mouse up from the previous slide’s mouse click.
That’s why the rogue Hint layer was appearing in our Storyline file. The “click outside” trigger was firing on the second slide, because the slide advanced from the first slide to the second slide in the split-second between the first slide’s mouse down and mouse up.
The way we resolved this was to add an extra layer (literally) in between the mouse down and the mouse up. On each slide that had the issue, we added a blank layer with no objects on it. The timeline is a quarter of a second, and we added a trigger to advance to the next slide when the timeline ends on this layer.
Then, on the base layer, we show the blank layer when the learner clicks the object we want them to click. This way, there’s a tiny stretch of time to account for the learner finishing their click before the slide advances, so they’re not still on mouse down when they get to the next slide. And we found that the extra quarter-second of “waiting” time isn’t noticeable.
We would still have an issue if a learner clicks their mouse and holds it down for longer than the quarter-second…so we might have to tweak the timing on that blank layer, but in general, I think it's a risk we can live with.
8 Replies
Which slide? I ran the file you attached, and did not see a problem.
Is it happening when a slide is revisited? In that case , either set the slide to Return to Initial state on Revisit, or add this trigger:
"Hide layer Hint when learner clicks hotspot". Be sure to add it before the jump trigger.
Thanks so much, Walt. When I get to the last slide 1.6 in preview the Hint slide layer displays. This happens on other slides and I just put a few slides together that were displaying this behavior. I know a few slides don't have hint layers.
it seems you have a problem similar to
https://community.articulate.com/discussions/articulate-storyline/storyline-hover-glitch-hover-doesn-t-work-on-whichever-part-the-mouse-is-on-when-the-slide-opens
-> user click from one slide triggers an action from the next slide (-> timing error)
it looks like hotspots are also affected by the (new ?) problem
fix: use normal rectangles (-> opacity 0) for the function as hotspot
rectangles with click trigger seems ok
https://360.articulate.com/review/content/344115be-7e88-404b-a915-db357ccb65b1/review
Hi Paul,
Great idea opening a chat case! I see you've connected with my teammate, Georvy, and you were able to fix the issue by recreating the corrupt slides.
Let me know if you have other questions. I'm more than happy to assist further!
@Eric, I am still having the same issues even when recreating slides - I do not think this is the fix. I would love to do a screen share, if possible, with a staff member.
Best,
Paul
All- even recreating a new project and inserting new slides and inserting elements (not copy/paste) produces the same error of the hint layer displaying prior to the user clicking outside of the rectangle area. #frustrated
SOLVED-
The “When user clicks” trigger is fired on mouse up, not on mouse down. So, if you click the mouse button down and hold it, nothing happens; once you unclick the mouse button, the trigger fires. That’s pretty standard web behavior—no issue there.
And in our case, that wouldn’t be an issue if the learner was using the NEXT button to advance the course; they’re clicking in the player, not on the slide. However, on some of our slides, the learner clicks an object on the slide to advance to the next slide. This is where our issue comes in: in our case, when we have two slides in a row that have the “When the user clicks outside [whatever object]” trigger, the second slide registers the mouse up from the previous slide’s mouse click.
That’s why the rogue Hint layer was appearing in our Storyline file. The “click outside” trigger was firing on the second slide, because the slide advanced from the first slide to the second slide in the split-second between the first slide’s mouse down and mouse up.
The way we resolved this was to add an extra layer (literally) in between the mouse down and the mouse up. On each slide that had the issue, we added a blank layer with no objects on it. The timeline is a quarter of a second, and we added a trigger to advance to the next slide when the timeline ends on this layer.
Then, on the base layer, we show the blank layer when the learner clicks the object we want them to click. This way, there’s a tiny stretch of time to account for the learner finishing their click before the slide advances, so they’re not still on mouse down when they get to the next slide. And we found that the extra quarter-second of “waiting” time isn’t noticeable.
We would still have an issue if a learner clicks their mouse and holds it down for longer than the quarter-second…so we might have to tweak the timing on that blank layer, but in general, I think it's a risk we can live with.