Forum Discussion
Buttons disappear after coming back to base layer
Hi,
I'm facing an issue with the functionality/visibility of buttons.
When testing the learning experience, the slide that has the 6 points/principles appears to have some lagging. After I click on one of the points and close the tab that opens, I sometimes face issues clicking on the other numbers. They either disappear or the hover function doesn't work for a bit (slide shown in attachments). Tried this on multiple laptops and it is the same issue.
Here is how it is set up:
When the user picks a number/principle and clicks on it, a new layer is opened. The layer will have a "close" button that once clicked will launch the trigger "hide this layer". The user then is brought back to the base layer where they can choose another number (the clicked one will appear in the visited state).
Link to experience:
https://360.articulate.com/review/content/c4f72169-2b3d-4b07-a77e-87179d92f95d/review
Thanks, appreciate the support.
Update: this seems to be mostly on desktop.
The mobile experience is smoother.
Just a wild guess, but the problem could be caused by "The user then is brought back to the base layer". Visiting a layer doesn't cause the learner to leave the base; it merely lays the layer over the base. (That's why it is called a layer.) The learner is always on the slide (what SL calls the base layer), so there is no "bringing back". When you hide the layer, the base becomes visible again. So if you are doing something to bring them back, that could cause issues.
On the other hand, the real problem could be something nowhere close to that, but it's hard to tell without seeing the project. For an actual accurate answer, attach the .story file here so someone can take a look at it,
Hi Walt,
What I meant by "brought back" is that the layer closes and the base layer is shown again. Here is another screenshot of what it looks like.
Hello Kaouther Akid,
Happy to help!
It would be super helpful if we could take a look at your project file so we could see what's happening. Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll delete it when we're done!
Hey, I found a way around it.
Removed, added, and rearranged some triggers and it is now working fine.
Thanks.
