Hotspots in Scrolling Panel

Feb 11, 2015

I have been struggling with trying to create a question slide within Storyline. Here's where I am at:

  • The question requires the learner to locate the item to select within a website image.
  • Due to the size of the image, I have added it into a scrolling panel.
  • A hotbox has been added into the scrolling panel and is following the item within the scrolling panel.
  • The hotbox is marked as the correct answer to the question.

When I try to preview the slide, I can use the scrolling panel to view the entire picture, but am unable to select the hotspot within the slide.

Has anyone else had this experience and able to provide any assistance on how to tackle this one? I have attached the story file to show the example...

17 Replies
Jamie Moorcroft-Sharp

My workaround for this has, sadly, been to jump directly to the slide with the hotspots/hyperlinks in a scroll box. I did some testing and the issue seems to occur when you Lightbox the slide with the hotspots/hyperlinks in the scroll box. 

See the attached file for an example of what I mean. Notice when you lightbox the second slide that the hyperlinks shift upward for the lower Terms. Whereas if you select the second slide in the menu you actually don't seem to have this issue at all.

Of course this doesn't help you if, like me, you're using Variables to trigger a certain definition to show once you Lightbox, or now Jump To, that particular slide. The way I work it is to have a definition for each term which is set to True when the user clicks it, and also Lighboxes the relevant glossary slide. I then have a trigger that shows the correct glossary layer on that slide when the timeline begins, if the Variable for that term is set to True, otherwise it won't show unless the Term is clicked.

My workaround will now be, I have to correct the entire thing, to have a Variable for each Slide. When the timeline starts on that slide, the Variable will be set to True. when the user clicks Next or Previous, the variable will be set to False. 

As before, the variables for each Glossary term will still change from False to True when they are clicked, but the hotspot that does this will also now Jump To the correct slide, for example, Glossary C. The glossary will work as intended, and then the user will click a close button in the top right, which I will add to each of my glossary Slides. The button will check for for Slide Variables that are set to True, and if they are True, for example Slide 1, then they will Jump To that slide. 

This is the workaround I will be using to ensure that the user is taken back to the Slide they are currently on in the course, therefore maintaining the current progression and not moving them away from where they are currently in the course.

Please do comment below and let me know if you have any questions. I've registered a ticket and hope that Articulate fix this soon, otherwise I hope my workaround serves you well.

Brandon Harper

That looks like it will work Jamie!

I have created a similar glossary and it seems to work well as a tool for our agents. Instead of using hotspots and variables, I used the hover state. When they roll over the term, the hover state highlights the term and shows the definition on the right. This made it easier to create and easier to use since there are less clicks to access the information. 

Arnau Fornell

Hi Michael, 

I was having more or less the same issue and that's why I came here looking for possible answers :) I applied the solution Michael Hinze offered and it worked. 

However, didn't you find it a bit unsatisfying from the user experience to click something and not have a mark or any proof that you indeed clicked in that spot?

In this regard, I've tried to use a shape that changes the state when clicked instead of a Hotspot but it does not stay locked at the place where it's supposed to be. I also tried to group the hotspot with the shape but no success. 

How did you manage in your course to get it done? 

Thanks and sorry to bring this up after some years. 




This discussion is closed. You can start a new discussion or contact Articulate Support.