Hotspots in Scrolling Panel

Hello Brandon,

This issue was reported to the QA team for review. Unfortunately there is not workaround for this, unless you can remove the scrolling panel from the question. If there are any updates, i will post it here.

As a workaround, you could use an offstage Pick-One Freeform question, as shown in the attached.

Thanks for sharing that idea Michael!

Thank you both for the assistance! I can make this work :-)

Glad to hear Brandon!

Was this issue ever resolved? I am currently having the same problem.

I used Michael's work-around and it worked perfectly for me. 

Hi Richard! Looks like this issue is still open with our QA Team.

Thanks Brandon for popping in to share that :)

I've been having a similar issue, but can't use this workaround because it's not a question I'm creating, it's a glossary. Any chance the issue has been fixed or you know of a workaround?

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.

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. 

I hadn't thought of that! That's another great way around it, does that solution work while the glossary is Lightboxed then?

Just mocked up an example for you to see. One "trick" was to add a small shape (in this case a line) at the bottom of the scroll panel to make it long enough to display the full hover. I hope this is helpful for you!

Thanks for that, it's really useful, probably the way I'll alter the glossary in the future

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. 

Arnau

Hi Arnau,

Brandon may no longer be subscribed to this discussion, so feel free to use the Contact Me button on his profile page if you'd like to reach out directly!

Hi Arnau! After so many years now, I honestly cannot recall how I did it back then. If you would like to share a file, perhaps I could take a look and see if I can help figure out a way to make things happen :-) I have become a master of finding the work-around on these kinds of things!